← Back to CVE intelligence
CVE intelligence

CVE-2026-99244

Vulnerability intelligence

Published Nov 3, 2026Sources checked Nov 19, 2026
N/ACVSS not listedScore unavailable
What this means

Review the available evidence

CVE-2026-99244. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - Cryptographic API; - File systems infrastructure; - Key management; - Key Management; - io_uring subsystem; - PID namespace; - Tracing infrastructure; (CVE-2026-99218, CVE-2026-99219, CVE-2026-99220, CVE-2026-99221, CVE-2026-99222, CVE-2026-99223, CVE-2026-99224, CVE-2026-99225, CVE-2026-99226, CVE-2026-99227, CVE-2026-99232, CVE-2026-99233, CVE-2026-99234, CVE-2026-99235, CVE-2026-99236, CVE-2026-99237, CVE-2026-99238, CVE-2026-99244, CVE-2026-99245)

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-99244?

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.

Source: NVD