CVE-2026-23148: Linux kernel · Race Condition
Affects Linux kernelSource CVE Database V5
Not known to be exploited · CVSS 7.5 High · fixed in ee10b06980acca1d46e0fa36d6fb4a9578eab6e4 : patch Linux kernel soon.
Data as of 26 Oct 2026, 17:30 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers can reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-10-16.
- Patch
- Available – fixed in ee10b06980acca1d46e0fa36d6fb4a9578eab6e4, 68207ceefd71cc74ce4e983fa9bd10c3122e349b, 6.16 +2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 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– |
AI-suggested
A fix is available in Linux kernel versions 6.12.69, 6.16, and later. Users and administrators should upgrade to these fixed versions to mitigate the vulnerability. No additional mitigations are indicated or required.
Description
A race condition in the Linux kernel's nvmet subsystem can cause a NULL pointer dereference leading to a kernel crash. The flaw occurs when a bio is re-submitted while its resources are being cleaned up, causing a use-after-free scenario. This vulnerability affects certain Linux kernel versions and has been fixed by reordering function calls to ensure proper cleanup before re-submission.