CVE-2026-99217

Process-creation hang via failed-fork cleanup deadlock

Published Nov 2, 2026 · Updated Nov 2, 2026

Deadlock in Linux fork cleanup allows local users to block system-wide process creation when fork failure races with BPF link closure. copy_process() calls exit_files() while holding scx_fork_rwsem for reading, and BPF scheduler teardown waits for the same lock for writing. Reachability requires the sched_ext BPF scheduler teardown path and the concurrent failure condition; the documented consequence is blocked forks, not a crash or data disclosure.

CVSS severityUnavailable
Unscored
EPSS probabilityUnavailable
No score available in this record
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Contact us

Summary

What happened

Deadlock in Linux fork cleanup allows local users to block system-wide process creation when fork failure races with BPF link closure. copy_process() calls exit_files() while holding scx_fork_rwsem for reading, and BPF scheduler teardown waits for the same lock for writing. Reachability requires the sched_ext BPF scheduler teardown path and the concurrent failure condition; the documented consequence is blocked forks, not a crash or data disclosure.

The record

CVE
CVE-2026-99217
Published
Nov 2, 2026
Updated
Nov 2, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
local
Privileges
Unavailable

Timeline

How it unfolded

  1. Nov 2, 2026CVE publishedPublication date reported by the CVE source.
  2. Nov 2, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.12.115
  2. Affected versionversion=0 <6.18.60
  3. Affected versionversion=0 <7.2.14
  4. Affected versionversion=0 <7.3.1
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <14c7de6ca239326b79fd3f7aee55dfada1bb72ab
  6. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <27e1cbf8ec5f7117f6bb2d2e44030ac055f09097
  7. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <afa8eb069694bd9f845e5e44eac6e81cbc06780e
  8. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f7ac8500d58e7684d37403553b1dea90ee2b27b1

What conditions does exploitation require?

Attack vectorlocal
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.12.115; version=0 <6.18.60; version=0 <7.2.14; version=0 <7.3.1; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <14c7de6ca239326b79fd3f7aee55dfada1bb72ab; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <27e1cbf8ec5f7117f6bb2d2e44030ac055f09097; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <afa8eb069694bd9f845e5e44eac6e81cbc06780e; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f7ac8500d58e7684d37403553b1dea90ee2b27b1

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Contact us