nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.113, 6.18.56, 7.2.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 28982ad73d6a9605708631dc49a0c763cc398aa2 · fixed in 44dc998c38fb5e153c3ed5665f1112661841c3f5; From 28982ad73d6a9605708631dc49a0c763cc398aa2 · fixed in 2d86abd28071481a1abd87204a47325975dc821c; From 28982ad73d6a9605708631dc49a0c763cc398aa2 · fixed in 8b85838c1fdba5ba90152693ca158aa9660c628f; From 28982ad73d6a9605708631dc49a0c763cc398aa2 · fixed in 4a5e49ba0abb8b4328d6318c9aef0c0121f95507
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.113; From 6.13.0 · fixed in 6.18.56; From 6.19.0 · fixed in 7.2.10