GHSA-7665-PCFF-X7HW
Vulnerability from github – Published: 2026-10-18 18:32 – Updated: 2026-10-18 18:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-98727"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-18T16:17:26Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nnvme-multipath: set BLK_FEAT_ZONED only after the zone info is known\n\nThe namespace head is marked zoned at allocation time based only on the\ncommand set identifier. If the zone info query reports a zero zone size,\nthe path namespace is registered without zoned limits while the head\nstill advertises the zoned capability with a zone size of zero, and\nreporting zones or writing to the head then shifts by ilog2(0).\n\nDrop the zoned feature from the head allocation and let the head limits\nrefresh stack it in from the path namespace instead.",
"id": "GHSA-7665-pcff-x7hw",
"modified": "2026-10-18T18:32:01Z",
"published": "2026-10-18T18:32:01Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98727"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2d86abd28071481a1abd87204a47325975dc821c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/44dc998c38fb5e153c3ed5665f1112661841c3f5"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/4a5e49ba0abb8b4328d6318c9aef0c0121f95507"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8b85838c1fdba5ba90152693ca158aa9660c628f"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.