Linux Kernel up to 7.2.12 pid_namespace zap_pid_ns_processes infinite loop

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
5.3$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 6.1.190/6.6.160/6.12.114/6.18.58/7.2.12. This vulnerability affects the function zap_pid_ns_processes of the component pid_namespace. The manipulation leads to infinite loop. This vulnerability is referenced as CVE-2026-99249. The attack can only be performed from a local environment. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.1.190/6.6.160/6.12.114/6.18.58/7.2.12. It has been rated as critical. This issue affects the function zap_pid_ns_processes of the component pid_namespace. The manipulation with an unknown input leads to a infinite loop vulnerability. Using CWE to declare the problem leads to CWE-835. The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop. Impacted is availability. The summary by CVE is:

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.

It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-99249 since 09/25/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 375578 (Linux Distros Unpatched Vulnerability : CVE-2026-99249), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 6.1.191, 6.6.161, 6.12.115, 6.18.59 or 7.2.13 eliminates this vulnerability. Applying the patch 064a6761d6f6ac55d090d3eaca649577ee736713/e8dafad7de9ede813af2d48cc04b7c88fef16682/4b47107f1a80c809c80093e872bcaccdbae13db4/2e10b8a74f55b5aae33db105d3e2d3ae759c865a/7deb5770840339fe88755bf27b92f74edc26ee87/81933038f5e273d17ed22792f906889393b204c5 is able to eliminate this problem. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (375578). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Infinite loop
CWE: CWE-835 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 375578
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-99249

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 6.1.191/6.6.161/6.12.115/6.18.59/7.2.13
Patch: 064a6761d6f6ac55d090d3eaca649577ee736713/e8dafad7de9ede813af2d48cc04b7c88fef16682/4b47107f1a80c809c80093e872bcaccdbae13db4/2e10b8a74f55b5aae33db105d3e2d3ae759c865a/7deb5770840339fe88755bf27b92f74edc26ee87/81933038f5e273d17ed22792f906889393b204c5

Timelineinfo

09/25/2026 CVE reserved
11/03/2026 +39 days Advisory disclosed
11/03/2026 +0 days VulDB entry created
11/04/2026 +1 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CNA: Linux
CVE: CVE-2026-99249 (🔒)

GCVE (CVE): GCVE-0-2026-99249
GCVE (VulDB): GCVE-100-430235

Entryinfo

Created: 11/03/2026 12:43
Updated: 11/04/2026 09:12
Changes: 11/03/2026 12:43 (59), 11/04/2026 09:12 (2)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!