# nvmet: fix max_qid race between configfs and controller allocation

CVE record · `CVE-2026-90206`

- **Identifiers:** `CVE-2026-90206`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 17 Sept 2026
- **Updated:** 30 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 17 Sept 2026, 16:07 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before cae0f5ed6ce7af3f7e0003c417f1953a350f55bf` (git)
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before af811970da4f0a928f5a1b1a946a04f755ce86f2` (git)
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before a1b88a1782eb6b368071dcda548a41b5c23d8cd2` (git)
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before 6e6f8e3bfc66dff1833a48ecfd857268cff3be84` (git)
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before 2c23fc91789dfd9db746edb3ae9b90d65fabd410` (git)
  - affected: `3e980f5995e0bb4d86fef873a9c9ad66721580d0 to before f1a8846e06388113dfdbb89dee005083fa9afdf9` (git)
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.1`
  - unaffected: `before 6.1` (semver)
  - unaffected: `6.1.191 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.160 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.114 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.57 to 6.18.*, inclusive` (semver)
  - unaffected: `7.2.6 to 7.2.*, inclusive` (semver)
  - unaffected: `7.3 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Linux kernel NVMe target (nvmet) has a race condition between the configfs max_qid attribute and controller allocation. If max_qid is changed while a new controller is being allocated, the queue array can be sized smaller than the queue ID limit, causing an out-of-bounds memory write. The source does not state what an attacker needs beyond the ability to modify the attribute, nor the full impact. Upgrade to a fixed Linux kernel version, which includes the commit cae0f5ed6ce7af3f7e0003c417f1953a350f55bf or a later stable release, such as 6.1.191 or later in the 6.1 series.

Written 12 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 17 Sept 2026. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2026-90206](https://www.cve.org/CVERecord?id=CVE-2026-90206)
- [NVD: CVE-2026-90206](https://nvd.nist.gov/vuln/detail/CVE-2026-90206)

### References from the CNA

- <https://git.kernel.org/stable/c/cae0f5ed6ce7af3f7e0003c417f1953a350f55bf>
- <https://git.kernel.org/stable/c/af811970da4f0a928f5a1b1a946a04f755ce86f2>
- <https://git.kernel.org/stable/c/a1b88a1782eb6b368071dcda548a41b5c23d8cd2>
- <https://git.kernel.org/stable/c/6e6f8e3bfc66dff1833a48ecfd857268cff3be84>
- <https://git.kernel.org/stable/c/2c23fc91789dfd9db746edb3ae9b90d65fabd410>
- <https://git.kernel.org/stable/c/f1a8846e06388113dfdbb89dee005083fa9afdf9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-90206>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-90206/>. Everything for agents: <https://agentprime.io/llms.txt>.