In the Linux kernel, the following vulnerability has been resolved: pidnamespace: make zappidnsprocesses() freezable When the init of a pid…
CVE-2026-99249
In the Linux kernel, the following vulnerability has been resolved: pidnamespace: make zappidnsprocesses() freezable When the init of a pid namespace exits, zappidnsprocesses() waits until all other pids in the namespace are freed. A tracer outside the namespace that does not reap its traced zombies keeps those pids allocated, so this wait has no upper bound, and while it lasts every suspend attempt fails: Freezing user space processes failed after 20.006 seconds (2 tasks refusing to freeze, wqbusy=0): Neither wait is freezable. The first loop sleeps in dowait(), which returns -ERESTARTSYS on the freezer's fake signal; the loop then clears TIFSIGPENDING and waits again without ever freezing. The final loop sleeps in TASKINTERRUPTIBLE, and since nothing clears TIFSIGPENDING there, schedule() returns immediately after the first freeze attempt and the task spins until the wait ends. Sleep in TASKINTERRUPTIBLE | TASKFREEZABLE in dowait(), so that the freezer can freeze tasks waiting there directly, and in TASKIDLE | TASKFREEZABLE in the final loop, like coredumptaskexit() does. This was hit with Chromium-based browsers: crashpad ptrace-attaches the threads of a crashed renderer, which…
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
- 3 November 2026
- Last updated
- 3 November 2026
- Assigner
- Linux
At the source
References
- https://git.kernel.org/stable/c/064a6761d6f6ac55d090d3eaca649577ee736713
- https://git.kernel.org/stable/c/e8dafad7de9ede813af2d48cc04b7c88fef16682
- https://git.kernel.org/stable/c/4b47107f1a80c809c80093e872bcaccdbae13db4
- https://git.kernel.org/stable/c/2e10b8a74f55b5aae33db105d3e2d3ae759c865a
- https://git.kernel.org/stable/c/7deb5770840339fe88755bf27b92f74edc26ee87
- https://git.kernel.org/stable/c/81933038f5e273d17ed22792f906889393b204c5
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.
Query this programmatically
Agents can read this through the MCP endpoint, or over HTTP:
curl https://cve.zerocrew.in/api/cve/CVE-2026-99249