CVE-2026-99249 linux linux
linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
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.
- EPSS
- 0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
- Published
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Fix and patched versions
- Linux Linux: fixed in 6.1.191
- Linux Linux: fixed in 6.6.161
- Linux Linux: fixed in 6.12.115
- Linux Linux: fixed in 6.18.59
- Linux Linux: fixed in 7.2.13
- Linux Linux: fixed in 7.3
- Debian, Ubuntu, Azure Linux, Alpaquita: fixed package versions per release
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-99249 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-99249?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-99249?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-99249 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Linux | 2.6.24 and later |
Fixed in
| Product | Release line | Fixed in |
|---|---|---|
| Linux | 6.1 | 6.1.191 |
| Linux | 6.6 | 6.6.161 |
| Linux | 6.12 | 6.12.115 |
| Linux | 6.18 | 6.18.59 |
| Linux | 7.2 | 7.2.13 |
| Linux | later releases | 7.3 |
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | linux | 6.1.192-1 | DEBIAN-CVE-2026-99249 |
| Debian | 12 | linux-6.12 | 6.12.115-2~deb12u1 | DEBIAN-CVE-2026-99249 |
| Debian | 13 | linux | 6.12.115-1 | DEBIAN-CVE-2026-99249 |
| Debian | 14 | linux | 7.2.13-1 | DEBIAN-CVE-2026-99249 |
| Ubuntu | 16.04:LTS | linux-hwe-edge | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 18.04:LTS | linux-gcp, linux-hwe, linux-oem and 12 more | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 20.04:LTS | linux-gke, linux-gkeop, linux-riscv and 26 more | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 22.04:LTS | linux, linux-aws, linux-gcp and 57 more | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 24.04:LTS | linux, linux-aws, linux-gcp and 50 more | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 26.04:LTS | linux, linux-aws, linux-gcp and 12 more | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | 26.10 | linux | 7.3.0-10.10 | UBUNTU-CVE-2026-99249 |
| Ubuntu | 26.10 | linux-aws, linux-gcp, linux-azure and 2 more | 7.3.0-1004.4 | UBUNTU-CVE-2026-99249 |
| Ubuntu | 26.10 | linux-azure-fde | 7.3.0-1004.5 | UBUNTU-CVE-2026-99249 |
| Ubuntu | 26.10 | linux-riscv, linux-realtime | 7.3.0-10.10.1 | UBUNTU-CVE-2026-99249 |
| Ubuntu | Nvidia-BlueField:22.04:LTS, Nvidia-BlueField:24.04:LTS | linux-bluefield | no fix listed | UBUNTU-CVE-2026-99249 |
| Ubuntu | Pro:14.04:LTS | linux, linux-aws, linux-azure and 1 more | no fix listed | UBUNTU-CVE-2026-99249 |
| 7 more for Ubuntu in the JSON and on Ubuntu's page. | ||||
| Azure Linux | 3 | kernel | 6.6.161.1-1 | AZL-112604 |
| Alpaquita | 23 | linux-lts | 6.1.191-r0 | BELL-CVE-2026-99249 |
| Alpaquita | 25 | linux-lts | 6.12.115-r0 | BELL-CVE-2026-99249 |
| Alpaquita | stream | linux-lts | 6.18.62-r0 | BELL-CVE-2026-99249 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.
References
- https://git.kernel.org/stable/c/064a6761d6f6ac55d090d3eaca649577ee736713
- https://git.kernel.org/stable/c/2e10b8a74f55b5aae33db105d3e2d3ae759c865a
- https://git.kernel.org/stable/c/4b47107f1a80c809c80093e872bcaccdbae13db4
- https://git.kernel.org/stable/c/7deb5770840339fe88755bf27b92f74edc26ee87
- https://git.kernel.org/stable/c/81933038f5e273d17ed22792f906889393b204c5
- https://git.kernel.org/stable/c/e8dafad7de9ede813af2d48cc04b7c88fef16682