{"id":"CVE-2026-99244","published":"2026-11-03T12:17:30.710","lastModified":"2026-11-03T20:18:30.743","description":"In the Linux kernel, the following vulnerability has been resolved:\n\npid_namespace: prevent TIF_NOTIFY_SIGNAL from interrupting the reaper\n\nSince commit 7fea700e04bd (\"zap_pid_ns_processes: clear\nTIF_NOTIFY_SIGNAL along with TIF_SIGPENDING\") zap_pid_ns_processes()\nclears TIF_NOTIFY_SIGNAL before every kernel_wait4() call. Otherwise\nkernel_wait4() doesn't sleep and returns -ERESTARTSYS if\nsignal_pending() is true and the reaper busy-waits.\n\nBut clearing TIF_NOTIFY_SIGNAL doesn't fix it. It can get raised again.\nFor example, klp_send_signals() sets it raw against any task that hasn't\ntransitioned yet. And it keeps sending it until the livepatch finishes.\n\nThe sleep loop waiting for pid_allocated to drop has the same problem\nand it doesn't even clear anything. So a schedule() in\nTASK_INTERRUPTIBLE returns immediately.\n\nUse a no_notify_signal guard. signal_pending() will ignore\nTIF_NOTIFY_SIGNAL and the pid namespace reaper sleeps until a child\nexits or free_pid() wakes it.","cvssScore":null,"cvssSeverity":null,"cvssVector":null,"cwes":[],"vendors":[],"products":[],"references":[{"url":"https://git.kernel.org/stable/c/2c20ace1698d03a23467351be1d281e89b36ade3","tags":[]},{"url":"https://git.kernel.org/stable/c/30b274508c743f243c82904954c4e416d7143d4c","tags":[]},{"url":"https://git.kernel.org/stable/c/3d15ac36ce174477efa5365e424dbd47950fd2b9","tags":[]},{"url":"https://git.kernel.org/stable/c/5c0985dd3c32fc2bbd0e8beaf13cf52cd97376a2","tags":[]},{"url":"https://git.kernel.org/stable/c/70178691c467c8f9f722765299fd8524c3121a35","tags":[]},{"url":"https://git.kernel.org/stable/c/9ab0324f4868eeb20c63f063a1e5bc01d5539212","tags":[]},{"url":"https://git.kernel.org/stable/c/f46cd8241d9b83f2279cc0db3e9d3e181b548a59","tags":[]}],"exploitRefs":[],"hasPoc":false,"ai":null}