CVE-2026-99561: fork: don't create io threads once PF_POSTCOREDUMP is set

Published Nov 19, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

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

zapprocess() skips every thread that already has PFPOSTCOREDUMP set. Such a thread is past synchronizegroupexit(), so a coredump can't catch it anymore. It isn't counted in corestate->threadsremaining and it isn't sent SIGKILL.

doexit() sets PFPOSTCOREDUMP in synchronizegroupexit() and calls iouringfilescancel() right after that. The cancellation runs task work and a createworkercb() 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. zapprocess() never saw it so it was never counted. But when it exits it sees signal->corestate in synchronizegroupexit() and decrements threadsremaining like any other thread.

So the count reaches zero one thread early and the dumper leaves coredumpwaitinactive() while a thread it counted is still running.

The task has no fatal signal pending because zapprocess() deliberately didn't send it one, and it never went through getsignal() so it doesn't have PFSIGNALED either.

Refuse to create an io thread when the creator has PFPOSTCOREDUMP. That costs nothing. iouringfilescancel() raises IOWQBITEXIT before it runs any task work, so a worker created from there only ever gets to exit again, and ioshouldretrythread() doesn't retry -EINTR.

Clearing PFPOSTCOREDUMP for the new thread in copyprocess() 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 zapprocess() has run is invisible to it whatever its flags say and still decrements threadsremaining 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 iouringfilescancel() ahead of synchronizegroupexit() 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 coredumptaskexit() 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 iouring work even before we did all the generic exit work.

Affected Software

4 affected componentsFixes available
linux/kernel>=5.16.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.2.15
7.2.15
linux/kernel>=7.3.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.2.15
  4. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:45 PM
Data Sourced
via MITRE·02:45 PM
Description
Data Sourced
via OSV·02:45 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203