# CVE-2026-68467: mtd: mchp23k256: use SPI match data for chip caps

> Incorrect MTD geometry selection for non-OF SPI matches in the mchp23k256 driver could lead to functional errors or data corruption.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68467, DEBIAN-CVE-2026-68467, GHSA-p34j-xw9f-x58x, UBUNTU-CVE-2026-68467

## What is CVE-2026-68467?

CVE-2026-68467 is a high-severity vulnerability in Linux, published on 15 Aug 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: mchp23k256: use SPI match data for chip caps

The driver stores chip capacity information in both the OF match table
and the SPI id table. Probe currently uses of_device_get_match_data(),
so a non-OF SPI modalias match falls back to mchp23k256_caps even when
the SPI id table selected a different part.

Use spi_get_device_match_data() so SPI id-table driver_data is consumed
when OF match data is absent. This keeps the existing default fallback
while avoiding the wrong MTD geometry for id-table-only matches.

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


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

Apply the vendor's patch.

## Is CVE-2026-68467 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68467 is a high-severity vulnerability in Linux, published on 15 Aug 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-68467 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-68467/ (Markdown: https://insights.sbomify.com/CVE-2026-68467/index.md)
```

## Sources

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

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