CPU exhaustion via PID-namespace reaper busy-wait
Published Nov 3, 2026 · Updated Nov 3, 2026
Busy-waiting in Linux PID-namespace teardown allows attackers to consume CPU via repeated task-work signal notifications. In zap_pid_ns_processes(), clearing TIF_NOTIFY_SIGNAL before kernel_wait4() does not prevent it from being raised again, and the pid_allocated wait loop also returns immediately instead of sleeping. The condition requires notifications during namespace teardown, with livepatch signaling given as an example; the record does not establish attacker privileges or a system crash.
Summary
What happened
Busy-waiting in Linux PID-namespace teardown allows attackers to consume CPU via repeated task-work signal notifications. In zap_pid_ns_processes(), clearing TIF_NOTIFY_SIGNAL before kernel_wait4() does not prevent it from being raised again, and the pid_allocated wait loop also returns immediately instead of sleeping. The condition requires notifications during namespace teardown, with livepatch signaling given as an example; the record does not establish attacker privileges or a system crash.
The record
- CVE
- CVE-2026-99244
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Nov 3, 2026CVE publishedPublication date reported by the CVE source.
- Nov 3, 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.
- Affected versionversion=09ab5b424b17cfe633db58bb2f9edbaf9484cf20
- Affected versionversion=3466abafa9f4f81a869da828e52a12f693175ec2 <9ab0324f4868eeb20c63f063a1e5bc01d5539212
- Affected versionversion=5.10.221 <5.11
- Affected versionversion=5.15.162 <5.16
- Affected versionversion=6.10
- Affected versionversion=6.1.95 <6.1.191
- Affected versionversion=6.6.35 <6.6.161
- Affected versionversion=6.9.6 <6.10
- Affected versionversion=7fea700e04bd3f424c2d836e98425782f97b494e <30b274508c743f243c82904954c4e416d7143d4c
- Affected versionversion=7fea700e04bd3f424c2d836e98425782f97b494e <3d15ac36ce174477efa5365e424dbd47950fd2b9
- Affected versionversion=7fea700e04bd3f424c2d836e98425782f97b494e <70178691c467c8f9f722765299fd8524c3121a35
- Affected versionversion=7fea700e04bd3f424c2d836e98425782f97b494e <f46cd8241d9b83f2279cc0db3e9d3e181b548a59
- Affected versionversion=82c7acf9a12c9b4e4b0aba531de82b4e39a345c8
- Affected versionversion=8e69e589f233ca2c9631f5af2b94f95dfc2ba804
- Affected versionversion=edd2754a62bee8d97b4808a15de024f66a1ddccf <2c20ace1698d03a23467351be1d281e89b36ade3
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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