CVE-2026-99249

pid_namespace: make zap_pid_ns_processes() freezable

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.

Key facts

Published
3 Nov 2026
Last changed
3 Nov 2026
Assigned by
Linux
EPSS
0.161% likely to be exploited in the next 30 days, higher than 5.347% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding 064a6761d6f6ac55d090d3eaca649577ee736713 (affected)
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding e8dafad7de9ede813af2d48cc04b7c88fef16682 (affected)
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding 4b47107f1a80c809c80093e872bcaccdbae13db4 (affected)
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding 2e10b8a74f55b5aae33db105d3e2d3ae759c865a (affected)
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding 7deb5770840339fe88755bf27b92f74edc26ee87 (affected)
  • 3eb07c8c8adb6f0572baba844ba2d9e501654316 up to but excluding 81933038f5e273d17ed22792f906889393b204c5 (affected)
LinuxLinux
  • Default status: affected
  • 2.6.24 (affected)
  • 0 up to but excluding 2.6.24 (unaffected)
  • 6.1.191 up to and including 6.1.* (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.2.13 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 3 Nov 2026 Published

References