Is there a public exploit for CVE-2026-99244?

No public exploit for CVE-2026-99244 was found in Exploit-DB, Metasploit, Nuclei templates or public proof-of-concept repositories. That is an absence of evidence rather than proof that none exists.

What does CVE-2026-99244 affect?

CVE-2026-99244 affects Linux Linux.

— Unscored

In the Linux kernel, the following vulnerability has been resolved: pidnamespace: prevent TIFNOTIFYSIGNAL from interrupting the reaper…

CVE-2026-99244

In the Linux kernel, the following vulnerability has been resolved: pidnamespace: prevent TIFNOTIFYSIGNAL from interrupting the reaper Since commit 7fea700e04bd ("zappidnsprocesses: clear TIFNOTIFYSIGNAL along with TIFSIGPENDING") zappidnsprocesses() clears TIFNOTIFYSIGNAL before every kernelwait4() call. Otherwise kernelwait4() doesn't sleep and returns -ERESTARTSYS if signalpending() is true and the reaper busy-waits. But clearing TIFNOTIFYSIGNAL doesn't fix it. It can get raised again. For example, klpsendsignals() 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 pidallocated to drop has the same problem and it doesn't even clear anything. So a schedule() in TASKINTERRUPTIBLE returns immediately. Use a nonotifysignal guard. signalpending() will ignore TIFNOTIFYSIGNAL and the pid namespace reaper sleeps until a child exits or freepid() wakes it.

Assessment

CVSS: Not yet scored
Severity: Unscored
Known exploited: Not listed in CISA KEV
Exploit availability: Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published: 3 November 2026
Last updated: 3 November 2026
Affected: Linux · Linux
Assigner: Linux

At the source

EUVD (ENISA)

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 5 + 7? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-99244