Skip to main content
VulnerabilityPublished

CVE-2026-99217: Linux kernel · fork: release the files of a failed fork after sched_cancel_fork()

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in f7ac8500d58e7684d37403553b1dea90ee2b27b1 : patch Linux kernel soon.

Data as of 2 Nov 2026, 16:43 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in f7ac8500d58e7684d37403553b1dea90ee2b27b1, afa8eb069694bd9f845e5e44eac6e81cbc06780e, 27e1cbf8ec5f7117f6bb2d2e44030ac055f09097 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • <6.12.115
  • <6.18.60
  • <7.2.14
  • <7.3.1
Fixed in
  • f7ac8500d58e7684d37403553b1dea90ee2b27b1
  • afa8eb069694bd9f845e5e44eac6e81cbc06780e
  • 27e1cbf8ec5f7117f6bb2d2e44030ac055f09097
  • 14c7de6ca239326b79fd3f7aee55dfada1bb72ab
  • 7.3.1
  • 7.2.14
  • 6.18.60
  • 6.12.115

AI-suggested

This vulnerability has been fixed in Linux kernel versions 6.12.115, 6.18.60, 7.2.14, and 7.3.1. Users and administrators should upgrade to these or later kernel versions to remediate the issue. No additional mitigation is required beyond applying the official fix.

Description

A vulnerability in the Linux kernel's fork implementation could cause a deadlock and system-wide fork blocking when a fork fails while another thread closes a BPF link file descriptor. The issue arises from improper cleanup of file references in failed forks, leading to a deadlock involving the scx_fork_rwsem lock. This has been fixed by reordering cleanup operations to release the child's files after sched_cancel_fork() drops the lock, preventing exit_files() from running on failed forks prematurely.

References

Community reviews

Loading reviews…