CVE-2026-90206: Linux kernel · nvmet: fix max_qid race between configfs and controller allocation
Source GCVE Database
Not known to be exploited · fixed in f1a8846e06388113dfdbb89dee005083fa9afdf9 : patch Linux kernel soon.
Data as of 30 Oct 2026, 19:03 UTC
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
Disclosed: evidence found.
CVE published 17 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
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
- nvd.nist.gov/vuln/detail/CVE-2026-90206 (opens in a new tab)
- git.kernel.org/stable/c/2c23fc91789dfd9db746edb3ae9b90d65fabd410 (opens in a new tab)
- git.kernel.org/stable/c/6e6f8e3bfc66dff1833a48ecfd857268cff3be84 (opens in a new tab)
- git.kernel.org/stable/c/a1b88a1782eb6b368071dcda548a41b5c23d8cd2 (opens in a new tab)
- git.kernel.org/stable/c/af811970da4f0a928f5a1b1a946a04f755ce86f2 (opens in a new tab)
- git.kernel.org/stable/c/cae0f5ed6ce7af3f7e0003c417f1953a350f55bf (opens in a new tab)
- git.kernel.org/stable/c/f1a8846e06388113dfdbb89dee005083fa9afdf9 (opens in a new tab)