Look up another CVE · open CVE-2026-98727 in the interactive tracker
CVE-2026-98727
nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known
Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/nvme. Debian urgency: unimportant.
What to do, per Debian release
Debian's own status for CVE-2026-98727 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 | not affected | 6.1.190-1 | Nothing to do. bookworm never shipped the vulnerable code. |
| Debian 13trixie | fixed | 6.12.113-1 | Update the kernel and reboot. Fixed in 6.12.113-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.10-1 | Update the kernel and reboot. Fixed in 7.2.10-1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
The namespace head is marked zoned at allocation time based only on the command set identifier. If the zone info query reports a zero zone size, the path namespace is registered without zoned limits while the head still advertises the zoned capability with a zone size of zero, and reporting zones or writing to the head then shifts by ilog2(0). Drop the zoned feature from the head allocation and let the head limits refresh stack it in from the path namespace instead.
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/nvme/host/multipath.c
- What this is
- NVM EXPRESS DRIVERMAINTAINERS section matched on drivers/nvme/host/ · linux-nvme@lists.infradead.org · Supported
- Kernel module
- nvme_core
Check it on the machine
grep -wE 'CONFIG_NVME_CORE|CONFIG_NVME_MULTIPATH' /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.
lsmod | grep -w nvme_corePrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this code. Every release below compiles the affected file into the kernels it ships.
- bookworm, trixie, forky, sidb
- b
- built in on some flavours, a module on others
- Build switches
- CONFIG_NVME_CORE, CONFIG_NVME_MULTIPATH
- 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-10-18 (today)source
- CVSS
- no vector published, unrated
- Attack vector
- not published
- EPSS
- not scored
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- unimportantsource
- Subsystem
- drivers/nvme
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 6.11 | 6.12.113 | 44dc998c38fb |
| 6.11 | 6.18.56 | 2d86abd28071 |
| 6.11 | 7.2.10 | 8b85838c1fdb |
| 6.11 | 7.3 | 4a5e49ba0abb |
Why the CNA scored it this way
The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98727, 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.