Skip to main content
VulnerabilityPublished Updated

CVE-2026-90206: Linux kernel · nvmet: fix max_qid race between configfs and controller allocation

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-90206· High

Not known to be exploited · fixed in f1a8846e06388113dfdbb89dee005083fa9afdf9 : patch Linux kernel soon.

Data as of 30 Oct 2026, 19:03 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f1a8846e06388113dfdbb89dee005083fa9afdf9, cae0f5ed6ce7af3f7e0003c417f1953a350f55bf, af811970da4f0a928f5a1b1a946a04f755ce86f2 +3

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < f1a8846e06388113dfdbb89dee005083fa9afdf9
Fixed in
  • f1a8846e06388113dfdbb89dee005083fa9afdf9
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < cae0f5ed6ce7af3f7e0003c417f1953a350f55bf
Fixed in
  • cae0f5ed6ce7af3f7e0003c417f1953a350f55bf
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < af811970da4f0a928f5a1b1a946a04f755ce86f2
Fixed in
  • af811970da4f0a928f5a1b1a946a04f755ce86f2
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < a1b88a1782eb6b368071dcda548a41b5c23d8cd2
Fixed in
  • a1b88a1782eb6b368071dcda548a41b5c23d8cd2
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < 6e6f8e3bfc66dff1833a48ecfd857268cff3be84
Fixed in
  • 6e6f8e3bfc66dff1833a48ecfd857268cff3be84
LinuxLinuxAffected
  • ≥ 3e980f5995e0bb4d86fef873a9c9ad66721580d0, < 2c23fc91789dfd9db746edb3ae9b90d65fabd410
Fixed in
  • 2c23fc91789dfd9db746edb3ae9b90d65fabd410

AI-suggested

A fix is available that protects queue allocations and controller list insertion with a read-write semaphore to prevent concurrent modification of max_qid during controller creation. Users should apply the official kernel patch that implements this synchronization to eliminate the race condition.

Description

A race condition in the Linux kernel's nvmet subsystem could lead to out-of-bounds memory access and potential memory corruption. This occurs when the max_qid attribute is modified concurrently with controller allocation, causing a mismatch between allocated memory size and usage. The issue is fixed by synchronizing access to the max_qid attribute during controller creation.

References

Community reviews

Loading reviews…