All reports
Medium

kernel: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-98727

Probability of exploitation in the next 30 days: 0.20%

FIRST EPSS · 2026-11-17

Description

In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known 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.

A flaw was found in the Linux kernel's NVMe (Non-Volatile Memory Express) multipath subsystem. The multipath driver inappropriately marks a storage device as supporting zoned storage before confirming its zone configuration. When a device reports a zone size of zero, subsequent read or write operations attempt an invalid mathematical shift calculation. A local user interacting with the affected storage device can exploit this flaw to crash the system, resulting in a Denial of Service (DoS).