CVE-2026-99230: Linux kernel · io_uring/cmd: don't leave list poison in ->hash_node
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in cc7f13d006fcefed9564bd79f135b51d344e9c77 : patch Linux kernel soon.
Data as of 2 Nov 2026, 16:31 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 cc7f13d006fcefed9564bd79f135b51d344e9c77, 685b49483200384d7f49d338af476e26e6824637, 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707
Exploitation evidence
Disclosed: evidence found.
CVE published 2 Nov 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 2 Nov 2026.
What to do
Upgrade Linux kernel to cc7f13d006fcefed9564bd79f135b51d344e9c77, 685b49483200384d7f49d338af476e26e6824637 or 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel in commits cc7f13d006fcefed9564bd79f135b51d344e9c77, 685b49483200384d7f49d338af476e26e6824637, and 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707. Users should update to a Linux kernel version including these commits to remediate the issue.
Description
A vulnerability in the Linux kernel io_uring subsystem was fixed to prevent leaving list poison values in the ->hash_node field. The issue occurs because io_uring_cmd_del_cancelable() uses hlist_del(), which leaves LIST_POISON1/2 markers behind. These poisoned pointers can cause a general protection fault and potential kernel memory corruption when requests are recycled without proper reinitialization. The flaw could lead to a kernel crash due to wild memory access.