Suspend failure via non-freezable namespace teardown
Published Nov 3, 2026 · Updated Nov 3, 2026
A freezer flaw in Linux PID-namespace teardown allows local users to block system suspend through unreaped traced zombies. In zap_pid_ns_processes(), waits for namespace processes to disappear cannot freeze, and a pending freezer signal makes the final wait spin instead of sleep. Triggering requires an exiting namespace init and an outside tracer retaining traced zombies; unprivileged reproduction requires user namespaces, and the suspend failure persists until the zombies are reaped or the tracer exits.
Summary
What happened
A freezer flaw in Linux PID-namespace teardown allows local users to block system suspend through unreaped traced zombies. In zap_pid_ns_processes(), waits for namespace processes to disappear cannot freeze, and a pending freezer signal makes the final wait spin instead of sleep. Triggering requires an exiting namespace init and an outside tracer retaining traced zombies; unprivileged reproduction requires user namespaces, and the suspend failure persists until the zombies are reaped or the tracer exits.
The record
- CVE
- CVE-2026-99249
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499
- Attack vector
- local
- Privileges
- authenticated
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=2.6.24
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <064a6761d6f6ac55d090d3eaca649577ee736713
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <2e10b8a74f55b5aae33db105d3e2d3ae759c865a
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <4b47107f1a80c809c80093e872bcaccdbae13db4
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <7deb5770840339fe88755bf27b92f74edc26ee87
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <81933038f5e273d17ed22792f906889393b204c5
- Affected versionversion=3eb07c8c8adb6f0572baba844ba2d9e501654316 <e8dafad7de9ede813af2d48cc04b7c88fef16682
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
- pidns-freeze-reproproof of concept · demonstrated
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