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

No public exploit for CVE-2026-99103 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: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a…

CVE-2026-99103

In the Linux kernel, the following vulnerability has been resolved: workqueue: Fix unbound pool lifetime for pending pwqs KASAN reports a use-after-free of an unbound workerpool in nodeactivatependingpwq(): BUG: KASAN: slab-use-after-free in rawspintrylock+0x6d/0x120 Read of size 4 at addr ffff8880089ce000 by task kworker/u22:0/318 CPU: 1 UID: 0 PID: 318 Comm: kworker/u22:0 Not tainted 7.2.0 #1 PREEMPT(lazy) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.15.0-1 04/01/2014 Workqueue: 0x0 (flush-8:0) Call Trace: dumpstacklvl+0x53/0x70 printreport+0xce/0x610 kasanreport+0xce/0x100 rawspintrylock+0x6d/0x120 pwqdecnrinflight+0x4b4/0xcb0 processonework+0x921/0x11a0 workerthread+0x4d0/0xd20 kthread+0x2de/0x3c0 retfromfork+0x3aa/0x620 retfromforkasm+0x1a/0x30 Allocated by task 311: allocpwq+0x439/0xca0 applywqattrsprepare+0x75e/0xd10 applyworkqueueattrslocked+0x44/0xa0 wqnicestore+0x350/0x450 Freed by task 0: kfree+0x127/0x3b0 rcucore+0x523/0x1780 handlesoftirqs+0x1b3/0x610 Last potentially related work creation: putunboundpool+0x3f3/0x7d0 pwqreleaseworkfn+0x494/0x8e0 kthreadworkerfn+0x1ff/0x790 Canceling the last inactive work skips pwqdecnractive(), so an empty pwq can…

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: 30 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 6 + 8? *

Query this programmatically

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

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