# CVE-2026-98727: nvme-multipath: set BLK_FEAT_ZONED only after the zone info is known

> A Linux kernel bug in NVMe multipath causes a crash when writing to a zoned namespace with zero zone size, requiring a patch.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98727, DEBIAN-CVE-2026-98727, GHSA-7665-pcff-x7hw, UBUNTU-CVE-2026-98727

## What is CVE-2026-98727?

CVE-2026-98727 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98727?


## How do I fix CVE-2026-98727?

Apply the vendor's patch.

## Is CVE-2026-98727 being exploited?

There is no known exploitation of CVE-2026-98727 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98727 and fix it if it is affected.

What it is: CVE-2026-98727 is a denial of service vulnerability in Linux, published on 18 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98727 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98727/ (Markdown: https://insights.sbomify.com/CVE-2026-98727/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98727
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98727
- OSV: https://osv.dev/vulnerability/CVE-2026-98727

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98727/
Summaries are generated and may contain mistakes; the official description above is the record.