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

No public exploit for CVE-2026-99205 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.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: sched/core: Call wakeuppreempt() for queued tasks during class change…

CVE-2026-99205

In the Linux kernel, the following vulnerability has been resolved: sched/core: Call wakeuppreempt() for queued tasks during class change Paul reported recent RCU changes exposed a lost resched where CPU idles with a rcutorture thread waiting while being completely runnable. Dumping the rq state at the time of idling with runnable tasks showed the following: rq->nextclass = &fairschedclass rq->nrrunning = 1 rq->cfs.hnrqueued = 0 rq->rt.rtnrrunning = 1 Although the waiting task was an RT task, "rq->nextclass" did not point to rtschedclass and was stuck at the lower priority fairschedclass. Inspecting schedchangeend() revealed the following race with schedsetscheduler() for queued, but non-running tasks: CPU0 CPU1 ==== ==== schedule() / rq->donor is a fair task that blocks. rq->nextclass = &fairschedclass / rqlock(rq0) picknexttask() / nrrunning = 0 / picktaskfair() schedbalancenewidle() rawspinrqunlock(rq0) rqlock(rq0) activatetask(rq0, p) / p is a fair task / rq0->nrrunning++; rq0->cfs.hnrqueued++; wakeuppreempt(rq, p) rq->nextclass = &fairschedclass reschedcurr() rqunlock(rq0) schedsetscheduler(p) / p is moved to SCHEDRR / taskrqlock(p) schedchangebegin() rq0->cfs.hnrqueued--;…

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: 28 October 2026
Last updated: 28 October 2026
Assigner: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

At the source

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

Query this programmatically

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

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