Skip to content
major vulnerability· requires attention

Linux kernel vulnerability in NVMe subsystem affects widely deployed OS kernels and could impact servers, clouds and endpoints broadly.

Systems

CVE-2026-97433

8.2
High
EPSS n/aPatch availableSep 26, 2026

Linux NVMe FDP parsing bug enables kernel memory corruption or crash

common questions

Is CVE-2026-97433 being exploited?

Not confirmed. CVE-2026-97433 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-97433?

CVE-2026-97433 is rated High with a CVSS score of 8.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-97433?

Yes. A fix has been recorded for CVE-2026-97433. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-97433 affect?

CVE-2026-97433 affects Linux kernel (nvme FDP parsing), Linux distributions with affected kernel versions, Cloud hosts/VMs using NVMe or passthrough. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-97433?

Apply vendor kernel updates and reboot affected hosts immediately

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (nvme FDP parsing)Linux distributions with affected kernel versionsCloud hosts/VMs using NVMe or passthrough
impact

Malformed NVMe FDP descriptors can cause unbounded iteration/reads leading to kernel crashes, info disclosure or local privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= 30b5f20bb2ddab013035399e5c7e6577da49320a and < 97efd7a41aac08b43ea2337c5913a2bc75484f9f
  • affected>= 30b5f20bb2ddab013035399e5c7e6577da49320a and < 0ef4daa6534a510d61ea67c8ad9bb5097b0dd5f8
  • affected6.16
vendor says fixed in< 6.16, >= 6.18.53 and <= 6.18.*, >= 7.2 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free