Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-99244pid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 39 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.20% · top 91% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected edd2754a62bee8d97b4808a15de024f66a1ddccf – < 2c20ace1698d03a23467351be1d281e89b36ade3
    • affected 3466abafa9f4f81a869da828e52a12f693175ec2 – < 9ab0324f4868eeb20c63f063a1e5bc01d5539212
    • affected 7fea700e04bd3f424c2d836e98425782f97b494e – < 30b274508c743f243c82904954c4e416d7143d4c
    • affected 7fea700e04bd3f424c2d836e98425782f97b494e – < 70178691c467c8f9f722765299fd8524c3121a35
    • affected 7fea700e04bd3f424c2d836e98425782f97b494e – < 3d15ac36ce174477efa5365e424dbd47950fd2b9
    • affected 7fea700e04bd3f424c2d836e98425782f97b494e – < f46cd8241d9b83f2279cc0db3e9d3e181b548a59
    • affected 7fea700e04bd3f424c2d836e98425782f97b494e – < 5c0985dd3c32fc2bbd0e8beaf13cf52cd97376a2
    • affected 82c7acf9a12c9b4e4b0aba531de82b4e39a345c8
    • affected 8e69e589f233ca2c9631f5af2b94f95dfc2ba804
    • affected 09ab5b424b17cfe633db58bb2f9edbaf9484cf20
    • affected 6.1.95 – < 6.1.191
    • affected 6.6.35 – < 6.6.161
    • affected 5.10.221 – < 5.11
    • affected 5.15.162 – < 5.16
    • affected 6.9.6 – < 6.10
  • Linux · Linux

    • affected 6.10
    • unaffected < 6.10
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.161 – ≤ 6.6.*
    • unaffected 6.12.115 – ≤ 6.12.*
    • unaffected 6.18.60 – ≤ 6.18.*
    • unaffected 7.2.14 – ≤ 7.2.*
    • unaffected 7.3.1 – ≤ 7.3.*
    • unaffected 7.4-rc1 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-99244 badge
[![CVE-2026-99244](https://cveledger.app/badge/CVE-2026-99244.svg)](https://cveledger.app/cve/CVE-2026-99244)

Record last updated .