# CVE-2026-89952: mtd: rawnand: validate ONFI extended parameter page sections

> A missing bounds check in the Linux kernel NAND driver allows attackers with physical access to trigger memory corruption via malformed ONFI parameter pages.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-101228, BELL-CVE-2026-89952, DEBIAN-CVE-2026-89952, GHSA-xvpp-cjh2-87mx, UBUNTU-CVE-2026-89952

## What is CVE-2026-89952?

CVE-2026-89952 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

mtd: rawnand: validate ONFI extended parameter page sections

nand_flash_detect_ext_param_page() allocates the length declared by the
ONFI parameter page, then treats the data as a fixed header followed by
variable-length sections. It reads that header and advances over sections
without first proving that the fixed page and each current section fit in
the allocation.

Reject pages shorter than the fixed header, track the remaining variable
area while walking sections, and require the ECC section to contain every
field read from struct onfi_ext_ecc_info. Use device-scoped diagnostics
that identify the malformed ONFI section.

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


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

Apply the vendor's patch.

## Is CVE-2026-89952 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-89952 is a memory corruption vulnerability in Linux, published on 16 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-89952 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-89952/ (Markdown: https://insights.sbomify.com/CVE-2026-89952/index.md)
```

## Sources

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

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