VulnerabilityPublished 2 Nov 2026

CVE-2026-99230: Linux kernel · io_uring/cmd: don't leave list poison in ->hash_node

Source GCVE Database

Compare

Authoritative record:CVE-2026-99230· High

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

Data as of 2 Nov 2026, 19:29 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 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-43w7-gr43-gv9h

What to do

Upgrade Linux kernel to cc7f13d006fcefed9564bd79f135b51d344e9c77, 685b49483200384d7f49d338af476e26e6824637 or 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 93b8cc60c37b9d17732b7a297e5dca29b50a990d, < cc7f13d006fcefed9564bd79f135b51d344e9c77	Fixed in cc7f13d006fcefed9564bd79f135b51d344e9c77
LinuxLinux	Affected ≥ 93b8cc60c37b9d17732b7a297e5dca29b50a990d, < 685b49483200384d7f49d338af476e26e6824637	Fixed in 685b49483200384d7f49d338af476e26e6824637
LinuxLinux	Affected ≥ 93b8cc60c37b9d17732b7a297e5dca29b50a990d, < 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707	Fixed in 2d5af21422060c088f6e4fb0f1e7dcf5bcdd6707
LinuxLinux	Affected =6.7	Fixed in–

AI-suggested

If you cannot patch yet, avoid triggering the specific vectored futex wait conditions that lead to this issue if possible.

Description

A vulnerability in the Linux kernel's io_uring command handling could lead to a general protection fault due to leftover list poison pointers in the hash_node structure. This occurs when commands are removed from a cancelable list but the associated pointers are not properly reinitialized before reuse. The flaw can cause kernel crashes triggered by specific futex wait operations.

Impact

This vulnerability can cause a kernel crash (general protection fault) due to wild memory access from dereferencing poisoned pointers in the kernel's hash_node structure. This can lead to denial of service by crashing the affected system. There is no indication of privilege escalation or data corruption beyond the crash.

Summary

The Linux kernel io_uring_cmd_del_cancelable() function removes commands from the cancelable_uring_cmd list using hlist_del(), which leaves LIST_POISON1/2 values in the ->hash_node pointer. Because requests are recycled without reinitializing ->hash_node, subsequent users of this node may operate on poisoned pointers. Specifically, if a vectored futex wait is woken while still queueing futexes, io_futexv_wait() does not add the request to the futex_list, leaving completion to task_work. The completion function io_futexv_complete() calls __io_futex_complete(), which uses hlist_del_init() assuming the node is unhashed. If the node was previously a cancelable uring_cmd, this leads to writing through LIST_POISON2, causing a general protection fault and potential kernel crash.

References

Community reviews

Loading reviews…