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

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

CVE-2026-99217 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: fork: release the files of a failed fork after schedcancelfork()…

CVE-2026-99217

In the Linux kernel, the following vulnerability has been resolved: fork: release the files of a failed fork after schedcancelfork() Reorder copyprocess() cleanup so schedfork() taking scxforkrwsem scxprefork() is safe and isn't held around exiting files. Right now, a fork that fails while another thread closed the bpf link fd will deadlock against its own read side. It also blocks every fork on the system: copyprocess() holds scxforkrwsem for read exitfiles() closefiles() filpclosesync() bpfscxunreg() kthreadflushwork() waits for the disable work scxrootdisable() percpudownwrite(&scxforkrwsem) Simply release the child's files after schedcancelfork() dropped the lock. The task starts out as a copy of its parent so p->files points to the parent's table until copyfiles() replaces it. exitfiles() must not run for a fork that failed before that. Clear p->files up front so exitfiles() is a no-op for those and make copyfiles() set it explicitly for CLONEFILES.

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

At the source

EUVD (ENISA)

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

Query this programmatically

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

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