Answer in brief
CVE-2026-98727 records a Unknown severity vulnerability in nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=28982ad73d6a9605708631dc49a0c763cc398aa2 <44dc998c38fb5e153c3ed5665f1112661841c3f5 || >=28982ad73d6a9605708631dc49a0c763cc398aa2 <2d86abd28071481a1abd87204a47325975dc821c || >=28982ad73d6a9605708631dc49a0c763cc398aa2 <8b85838c1fdba5ba90152693ca158aa9660c628f || >=28982ad73d6a9605708631dc49a0c763cc398aa2 <4a5e49ba0abb8b4328d6318c9aef0c0121f95507 | 44dc998c38fb5e153c3ed5665f1112661841c3f5, 2d86abd28071481a1abd87204a47325975dc821c, 8b85838c1fdba5ba90152693ca158aa9660c628f, 4a5e49ba0abb8b4328d6318c9aef0c0121f95507 |
| Linux/Linuxgeneric | 6.11 | Not reported |
Published upstream
Oct 18, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 18, 2026
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.
Quoted source text, attributed separately from HOL analysis.