CVE Professor
›
Back
CVE-2026-99561

CVE-2026-99561 — Linux Linux (3a0cdf3eb9c3026b046efe32f01b9090ab4e2d73) — NONE Vulnerability

NONE CVSS 0 NVD+CVE.org

CVE-2026-99561 is a NONE severity security vulnerability (CVSS 0.0/10) affecting Linux Linux (3a0cdf3eb9c3026b046efe32f01b9090ab4e2d73). Technical vector analysis shows that an attacker can exploit this flaw remotely over the network without authentication (PR:N) with zero user interaction (UI:N), posing a direct security risk to affected deployments.

📄 Official NVD / MITRE Original Record Text

In the Linux kernel, the following vulnerability has been resolved: fork: don't create io threads once PF_POSTCOREDUMP is set zap_process() skips every thread that already has PF_POSTCOREDUMP set. Such a thread is past synchronize_group_exit(), so a coredump can't catch it anymore. It isn't counted in core_state->threads_remaining and it isn't sent SIGKILL. do_exit() sets PF_POSTCOREDUMP in synchronize_group_exit() and calls io_uring_files_cancel() right after that. The cancellation runs task work and a create_worker_cb() that io-wq queued before the exit creates a new io-wq worker from there. If another thread started a coredump in the meantime that worker joins a thread-group which is already being dumped. zap_process() never saw it so it was never counted. But when it exits it sees signal->core_state in synchronize_group_exit() and decrements threads_remaining like any other thread. So the count reaches zero one thread early and the dumper leaves coredump_wait_inactive() while a thread it counted is still running. The task has no fatal signal pending because zap_process() deliberately didn't send it one, and it never went through get_signal() so it doesn't have PF_SIGNALED either. Refuse to create an io thread when the creator has PF_POSTCOREDUMP. That costs nothing. io_uring_files_cancel() raises IO_WQ_BIT_EXIT before it runs any task work, so a worker created from there only ever gets to exit again, and io_should_retry_thread() doesn't retry -EINTR. Clearing PF_POSTCOREDUMP for the new thread in copy_process() was the other option. It makes the worker a thread like any other, but it only helps while the dump hasn't started. A worker born after zap_process() has run is invisible to it whatever its flags say and still decrements threads_remaining on the way out. Refusing to create it covers both, and then no task is ever born with the flag, so there is nothing to clear. Moving io_uring_files_cancel() ahead of synchronize_group_exit() closes the same window. It runs the cancellation, and whatever that can block on, before the thread announces itself to the dumper. A thread that blocks there never reaches coredump_task_exit() at all, so the dumper ends up waiting for a thread that never parks. Refusing the creation leaves the cancellation where it is. But it's very ugly to run io_uring work even before we did all the generic exit work.

Published 19.11.2026
ISO Date 2026-11-19
Source NVD+CVE.org
AI Security Analysis & Remediation
🤖 Generating Deep AI Security Analysis…
Analyzing CVSS vector & CWE weakness structure…

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-99561
CVSS 0/10 · UNKNOWN · 19.11.2026
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

🎯 WHAT IS THIS VULNERABILITY?
Summary: In the Linux kernel, the following vulnerability has been resolved:

fork: don't create io threads once PF_POSTCOREDUMP is set

zap_process() skips every thread that already has PF_POSTCOREDUMP set. Such a thread is past synchronize_group_exit(), so a coredump can't
catch it anymore. It isn't counted in core_state->threads_remaining and
it isn't sent SIGKILL.
Affected: Linux:Linux, Linux:Linux

⚡ ATTACK CHAIN
CVSS vector not available. Review vendor advisory.

🌍 REAL WORLD IMPACT

🛡️ REMEDIATION
→ Apply vendor security update for Linux:Linux.
→ Add WAF rule, create IDS alert for anomalous traffic.

⚠️ URGENCY
📌 Low priority — routine update sufficient.

────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]

Target Reconnaissance Queries (FOFA & Shodan)

FOFA Query

app="Linux Linux"
CVSS Score
0 / 10 · CVSS NONE
Affected Products (2)
Linux:Linux (3a0cdf3eb9c3026b046efe32f01b9090ab4e2d73) Linux:Linux (5.16)
Related CVEs
0.0
CVE-2026-108687
The SAML SSO Login WordPress plugin through 1.5.2 does not verify that the SAML assertion whose signature it
0.0
CVE-2026-121852
The AppPresser WordPress plugin before 5.0.0 does not properly escape the contents of its debug log when disp
0.0
CVE-2026-129446
The WPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) WordPress plugin before 45.4 does not
0.0
CVE-2026-120404
The built-in regular expression name finder for latitude and longitude coordinates uses a pattern that is vuln
0.0
CVE-2026-99321
In the Linux kernel, the following vulnerability has been resolved: rust_binder: wake epoll on self-work queu
0.0
CVE-2026-99322
In the Linux kernel, the following vulnerability has been resolved: ksmbd: rebind completed CREATE replays wi