Look up another CVE · open CVE-2026-80597 in the interactive tracker
CVE-2026-80597
mtd: maps: vmu-flash: fix NULL pointer dereference in initialization
Published 2026-08-28 (2 months ago) by the Linux kernel CNA. Subsystem drivers/mtd. Debian urgency: not yet assigned.
Debian does not build this code. The per-release build detail is under "Where it lives" below.
What to do, per Debian release
Debian's own status for CVE-2026-80597 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | fixed | 6.1.180-1 | Update the kernel and reboot. Fixed in 6.1.180-1. A running kernel keeps the old code until the machine restarts. |
| Debian 13trixie | fixed | 6.12.100-1 | Update the kernel and reboot. Fixed in 6.12.100-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.1.5-1 | Update the kernel and reboot. Fixed in 7.1.5-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The mtd_info contains a struct device, which must be linked to its parent. Without this, the initialization of the MTD fails with a NULL pointer dereference.
Where it lives
The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.
drivers/mtd/maps/vmu-flash.c
- What this is
- MEMORY TECHNOLOGY DEVICES (MTD)MAINTAINERS section matched on drivers/mtd/ · linux-mtd@lists.infradead.org · Maintained
- Kernel module
- none to look for. The file would have gone into vmu_flash, and Debian does not compile it into that module, so finding vmu_flash in lsmod would say nothing about this CVE.
Check it on the machine
grep -wE 'CONFIG_MTD|CONFIG_MTD_VMU' /boot/config-$(uname -r)Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.
Show whether Debian builds this, per release
Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.
- bookworm, trixie, forky, sidn
- n
- not enabled on any flavour - this release does not build the code
- Build switches
- CONFIG_MTD, CONFIG_MTD_VMU
- Reads as
- all on means the file is compiled; any one off means it is not.
From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages
Signals
- Published
- 2026-08-28 (2 months ago)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- 0.22%, higher than 11.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/mtd
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 2.6.30 | 5.10.261 | ff6453502c72 |
| 2.6.30 | 5.15.212 | c60a627edbbd |
| 2.6.30 | 6.1.178 | 0db62da830ec |
| 2.6.30 | 6.6.145 | 44c6abf5d823 |
| 2.6.30 | 6.12.97 | b80a7b8f1a10 |
| 2.6.30 | 6.18.40 | 9ac007affa77 |
| 2.6.30 | 7.1.5 | f4599793240d |
| 2.6.30 | 7.2 | 357e3b8e3a87 |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-80597, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.