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

No public exploit for CVE-2026-99207 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: scsi: target: Disable interrupts while holding delayedcmdlock…

CVE-2026-99207

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Disable interrupts while holding delayedcmdlock targetdodelayedwork() takes dev->delayedcmdlock with a plain spinlock(). It runs from systempercpuwq, so interrupts stay enabled while the lock is held. Every other acquisition of that lock uses spinlockirqsave(): targethandletaskattr() and transportcompleteorderedsync() in targetcoretransport.c, and targetnonorderedrelease() in targetcoredevice.c. That was safe while every caller of transportcompletetaskattr() ran in process context: targetcompleteokwork() from targetcompletionwq, transportcompleteqf() from dev->qfworkqueue, and transportgenericrequestfailure() from the submit and execute paths. Since commit 06933066d88a ("scsi: target: Add support for completing commands from backend context") that is no longer true. With completetype=1 on a fabric that sets directcomplsupp, targetcomplete() runs targetcompleteokwork() inline in the backend's completion context, which targetcompletecmdwithsense() documents as "May be called from interrupt context". For iblock that is the bio endio. targetcompleteokwork() starts with transportcompletetaskattr(), which…

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 9 + 6? *

Query this programmatically

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

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