CVE-2026-99244: pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 2c20ace1698d03a23467351be1d281e89b36ade3, 30b274508c743f243c82904954c4e416d7143d4c, 3d15ac36ce174477efa5365e424dbd47950fd2b9.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 2c20ace1698d03a23467351be1d281e89b36ade3, 30b274508c743f243c82904954c4e416d7143d4c, 3d15ac36ce174477efa5365e424dbd47950fd2b9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper Since commit 7fea700e04bd ("zap_pid_ns_processes: clear TIF_NOTIFY_SIGNAL along with TIF_SIGPENDING") zap_pid_ns_processes() clears TIF_NOTIFY_SIGNAL before every kernel_wait4() call. Otherwise kernel_wait4() doesn't sleep and returns -ERESTARTSYS if signal_pending() is true and the reaper busy-waits. But clearing TIF_NOTIFY_SIGNAL doesn't fix it. It can get raised again. For example, klp_send_signals() sets it raw against any task that hasn't transitioned yet. And it keeps sending it until the livepatch finishes. The sleep loop waiting for pid_allocated to drop has the same problem and it doesn't even clear anything. So a schedule() in TASK_INTERRUPTIBLE returns immediately. Use a no_notify_signal guard. signal_pending() will ignore TIF_NOTIFY_SIGNAL and the pid namespace reaper sleeps until a child exits or free_pid() wakes it.
- Published
- Nov 3, 2026
- Updated
- Nov 3, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 82c7acf9a12c9b4e4b0aba531de82b4e39a345c8, 8e69e589f233ca2c9631f5af2b94f95dfc2ba804, 09ab5b424b17cfe633db58bb2f9edbaf9484cf20, 6.10affected
- edd2754a62bee8d97b4808a15de024f66a1ddccf and later · before 2c20ace1698d03a23467351be1d281e89b36ade3affected · git
- 3466abafa9f4f81a869da828e52a12f693175ec2 and later · before 9ab0324f4868eeb20c63f063a1e5bc01d5539212affected · git
- 7fea700e04bd3f424c2d836e98425782f97b494e and later · before 30b274508c743f243c82904954c4e416d7143d4caffected · git
- 7fea700e04bd3f424c2d836e98425782f97b494e and later · before 70178691c467c8f9f722765299fd8524c3121a35affected · git
- 7fea700e04bd3f424c2d836e98425782f97b494e and later · before 3d15ac36ce174477efa5365e424dbd47950fd2b9affected · git
- 7fea700e04bd3f424c2d836e98425782f97b494e and later · before f46cd8241d9b83f2279cc0db3e9d3e181b548a59affected · git
- 7fea700e04bd3f424c2d836e98425782f97b494e and later · before 5c0985dd3c32fc2bbd0e8beaf13cf52cd97376a2affected · git
- 6.1.95 and later · before 6.1.191affected · semver
- 6.6.35 and later · before 6.6.161affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:13 | linux | before 6.12.115-1 | 6.12.115-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-99241Nov 2, 2026 · ntfs: take invalidate_lock in ntfs_filemap_page_mkwrite()0Monitor
- ← EarlierCVE-2026-99242Nov 2, 2026 · ntfs: fix race between fallocate and mmap reads0Monitor
- Later →CVE-2026-99245Nov 3, 2026 · KEYS: Fix key_reject_and_link() race with keyring restriction0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2c20ace1698d03a23467351be1d281e89b36ade3 | Vendor (CNA) |
| Linux Linux | 30b274508c743f243c82904954c4e416d7143d4c | Vendor (CNA) |
| Linux Linux | 3d15ac36ce174477efa5365e424dbd47950fd2b9 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 5c0985dd3c32fc2bbd0e8beaf13cf52cd97376a2 | Vendor (CNA) |
| Linux Linux | 6.1.191 | Vendor (CNA) |
| Linux Linux | 6.10 | Vendor (CNA) |
| Linux Linux | 6.6.161 | Vendor (CNA) |
| Linux Linux | 70178691c467c8f9f722765299fd8524c3121a35 | Vendor (CNA) |
| Linux Linux | 9ab0324f4868eeb20c63f063a1e5bc01d5539212 | Vendor (CNA) |
| Linux Linux | f46cd8241d9b83f2279cc0db3e9d3e181b548a59 | Vendor (CNA) |
| debian:linux | 6.12.115-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 7, 2026+4 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1451 · Nov 4, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
- git.kernel.org/stable/c/30b274508c743f243c82904954c4e416d7143d4c
- git.kernel.org/stable/c/3d15ac36ce174477efa5365e424dbd47950fd2b9
- git.kernel.org/stable/c/5c0985dd3c32fc2bbd0e8beaf13cf52cd97376a2
- git.kernel.org/stable/c/70178691c467c8f9f722765299fd8524c3121a35
- git.kernel.org/stable/c/9ab0324f4868eeb20c63f063a1e5bc01d5539212
- git.kernel.org/stable/c/f46cd8241d9b83f2279cc0db3e9d3e181b548a59
Vendor advisories and official records. Exploit/PoC links are deliberately left out.