Is there a public exploit for CVE-2026-99230?

No public exploit for CVE-2026-99230 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

What does CVE-2026-99230 affect?

CVE-2026-99230 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: iouring/cmd: don't leave list poison in ->hashnode…

CVE-2026-99230

In the Linux kernel, the following vulnerability has been resolved: iouring/cmd: don't leave list poison in ->hashnode iouringcmddelcancelable() uses hlistdel() to take a command off cancelableuringcmd, which leaves LISTPOISON1/2 behind in hashnode. Requests are recycled through the request cache without being reinitialised, and not every user of ->hashnode sets it up before it is used: If a vectored futex wait is woken while futexwaitmultiplesetup() is still queueing the futexes, iofutexvwait() doesn't add the request to futexlist, and leaves the completion to the taskwork queued by the wake up. iofutexvcomplete() ends in iofutexcomplete(), whose hlistdelinit() is fine for a request that is unhashed, which is how all other users of the node leave it. If the request was a cancelable uringcmd in its previous life, e.g. a ublk FETCHREQ, it writes through LISTPOISON2: Oops: general protection fault, probably for non-canonical address KASAN: maybe wild-memory-access in range [0xdead000000000120-...] RIP: 0010:iofutexvcomplete+0x219/0x420 Call Trace: tctxtaskworkrun+0x804/0x950 tctxtaskwork+0x71/0xa0 taskworkrun+0x118/0x200 Leave the node unhashed.

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 2 November 2026
Last updated: 2 November 2026
Affected: Linux · Linux
Assigner: Linux

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 4? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99230