# CVE-2026-97433: nvme: validate FDP configuration descriptor sizes

> An attacker can cause a denial of service in the Linux kernel NVMe driver by triggering unbounded iteration or out-of-bounds reads via malformed FDP configuration descriptors.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** AZL-103772, BELL-CVE-2026-97433, DEBIAN-CVE-2026-97433, GHSA-5h8w-586w-g6hj, UBUNTU-CVE-2026-97433

## What is CVE-2026-97433?

CVE-2026-97433 is a high-severity denial of service vulnerability in Linux, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

nvme: validate FDP configuration descriptor sizes

Validate descriptor sizes while walking the FDP configurations log so
dsze == 0 or a descriptor past the log end cannot cause unbounded
iteration or reads past the buffer.

## Which versions are affected by CVE-2026-97433?


## How do I fix CVE-2026-97433?

Apply the vendor's patch.

## Is CVE-2026-97433 being exploited?

There is no known exploitation of CVE-2026-97433 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97433 and fix it if it is affected.

What it is: CVE-2026-97433 is a high-severity denial of service vulnerability in Linux, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97433 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97433/ (Markdown: https://insights.sbomify.com/CVE-2026-97433/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97433
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97433
- OSV: https://osv.dev/vulnerability/CVE-2026-97433

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97433/
Summaries are generated and may contain mistakes; the official description above is the record.