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

No public exploit for CVE-2026-99202 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: libsas: Fix SMP IO deadlock during HA resume smpexecutetasksg()…

CVE-2026-99202

In the Linux kernel, the following vulnerability has been resolved: scsi: libsas: Fix SMP IO deadlock during HA resume smpexecutetasksg() calls pmruntimegetsync() on the host before issuing an SMP command. When that command is itself issued from the HA resume path, the getsync() deadlocks: it waits for the ongoing resume (the device is RPMRESUMING), while the resume is blocked in sasdrainwork() waiting for that same SMP IO to complete. The deadlock needs an expander-attached SATA disk. During sasresumeha() -> sasdrainwork(), DISCERESUME -> sasresumesata() atasasportresume() requests ATAEHRESET, and the hard reset for such a disk is done via SMP PHY CONTROL (sasatahardreset() -> sasphyreset() -> sassmpphycontrol() -> smpexecutetasksg()). Direct-attached SATA resets through llddcontrolphy() and SSP devices use TMFs, so neither hits this. Replace the getsync()/putsync() pair with pmruntimegetnoresume()/pmruntimeput(). smpexecutetasksg() only needs to hold off autosuspend while the SMP is in flight, and it must not try to resume the host: a sync resume issued from the HA resume path itself is what deadlocks, and by the time sasresumeha() runs, hwinit has already reinitialized the…

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

Query this programmatically

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

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