Skip to content
Threat Brief

← All advisories

CVE-2026-99561

Severity unknownNo known exploitationFix available

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

Record last updated

CVSS score

None

No score published yet

EPSS, chance of exploitation in 30 days

0.2%

Higher than 5% of scored CVEs. A prediction, not evidence.

CISA remediation deadline

None

Not in the KEV catalog

Description

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.

Patching and mitigation

Patch status
Fix available (source: CVE record (Linux))
Fix documented (source date)
Mitigation
None documented
Vendor guidance
No vendor link on record

Affected products

VendorProductAffected versionsFixed inPer
LinuxLinuxfrom 92307383082daff5df884a25df9e283efb7ef261 before 3a0cdf3eb9c3026b046efe32f01b9090ab4e2d733a0cdf3eb9c3026b046efe32f01b9090ab4e2d73CVE Program
LinuxLinuxfrom 92307383082daff5df884a25df9e283efb7ef261 before 64f2a38a1658493d7a53d656bcc483ee4b83762364f2a38a1658493d7a53d656bcc483ee4b837623CVE Program
LinuxLinuxfrom 92307383082daff5df884a25df9e283efb7ef261 before 9dea2e237ffe2a325b9d42ed15ea9ee6561979c79dea2e237ffe2a325b9d42ed15ea9ee6561979c7CVE Program
LinuxLinuxfrom 92307383082daff5df884a25df9e283efb7ef261 before 026aa32c00b0b3ea849d0ae98313274c9d3c7e21026aa32c00b0b3ea849d0ae98313274c9d3c7e21CVE Program
LinuxLinuxfrom 92307383082daff5df884a25df9e283efb7ef261 before 1f978881ce6c9ac4f4d4a7b6a6e52339eadcd3501f978881ce6c9ac4f4d4a7b6a6e52339eadcd350CVE Program
LinuxLinux5.16Not documentedCVE Program
LinuxLinux (unaffected)from 6.12.117 up to and including 6.12.*Not documentedCVE Program
LinuxLinux (unaffected)from 6.18.61 up to and including 6.18.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.2.15 up to and including 7.2.*Not documentedCVE Program
LinuxLinux (unaffected)from 7.3.2 up to and including 7.3.*Not documentedCVE Program
LinuxLinux (unaffected)7.4-rc1Not documentedCVE Program
LinuxLinux (unaffected)all versions before 5.16Not documentedCVE Program

Timeline

  1. Disclosure

    CVE record published by Linux

    Source: CVE Program (opens in a new tab)

  2. Patch

    Fix documented by CVE record (Linux)

    Source: CVE record (Linux) (opens in a new tab)

Vendor guidance and references