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

No public exploit for CVE-2026-99252 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-99252 affect?

CVE-2026-99252 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: iouring/mpscq: disable preemption while pushing A push makes the node…

CVE-2026-99252

In the Linux kernel, the following vulnerability has been resolved: iouring/mpscq: disable preemption while pushing A push makes the node the new tail, and then links it to its predecessor. In between the queue isn't empty, but mpscqpop() can't get at the node. The consumers deal with that by trying again, with a condresched() in the loop to give a preempted producer the chance to finish. condresched() doesn't do that if the consumer has a higher priority than the producer and both have to use the same CPU: producer (SCHEDOTHER) consumer (SCHEDFIFO), same CPU ioreqlocalworkadd() mpscqpush() prev = xchg(&q->tail, node) iocqringwait() iorunlocalwork() again: condresched() // nothing to do mpscqpop() // NULL // work pending, no events yet goto again The producer can be any task that is able to queue taskwork for the ring: an io-wq worker, or somebody who sends a message with IORINGOPMSGRING. The consumer spins, holding ->uringlock, until the scheduler takes pity on the fair class, which takes about a second with the default settings of the fair server, and forever without it. The loops in tctxtaskworkrun() and iocancellocaltaskwork() have the same problem. Don't allow preemption…

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: 3 November 2026
Last updated: 3 November 2026
Affected: Linux · Linux
Assigner: Linux

At the source

EUVD (ENISA)

References

https://git.kernel.org/stable/c/8c94677e2b6145393d4c129fe0f5364b0e5000a5

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 7 + 5? *

Query this programmatically

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

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