{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-99561","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2026-09-25T10:25:14.422Z","datePublished":"2026-11-19T14:45:39.370Z","dateUpdated":"2026-11-19T14:45:39.370Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-11-19T14:45:39.370Z"},"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfork: don't create io threads once PF_POSTCOREDUMP is set\n\nzap_process() skips every thread that already has PF_POSTCOREDUMP set.\nSuch a thread is past synchronize_group_exit(), so a coredump can't\ncatch it anymore. It isn't counted in core_state->threads_remaining and\nit isn't sent SIGKILL.\n\ndo_exit() sets PF_POSTCOREDUMP in synchronize_group_exit() and calls\nio_uring_files_cancel() right after that. The cancellation runs task\nwork and a create_worker_cb() that io-wq queued before the exit creates\na new io-wq worker from there. If another thread started a coredump in\nthe meantime that worker joins a thread-group which is already being\ndumped. zap_process() never saw it so it was never counted. But when it\nexits it sees signal->core_state in synchronize_group_exit() and\ndecrements threads_remaining like any other thread.\n\nSo the count reaches zero one thread early and the dumper leaves\ncoredump_wait_inactive() while a thread it counted is still running.\n\nThe task has no fatal signal pending because zap_process() deliberately\ndidn't send it one, and it never went through get_signal() so it doesn't\nhave PF_SIGNALED either.\n\nRefuse to create an io thread when the creator has PF_POSTCOREDUMP.\nThat costs nothing. io_uring_files_cancel() raises IO_WQ_BIT_EXIT\nbefore it runs any task work, so a worker created from there only ever\ngets to exit again, and io_should_retry_thread() doesn't retry -EINTR.\n\nClearing PF_POSTCOREDUMP for the new thread in copy_process() was the\nother option. It makes the worker a thread like any other, but it only\nhelps while the dump hasn't started. A worker born after zap_process()\nhas run is invisible to it whatever its flags say and still decrements\nthreads_remaining on the way out. Refusing to create it covers both, and\nthen no task is ever born with the flag, so there is nothing to clear.\n\nMoving io_uring_files_cancel() ahead of synchronize_group_exit() closes\nthe same window. It runs the cancellation, and whatever that can block\non, before the thread announces itself to the dumper. A thread that\nblocks there never reaches coredump_task_exit() at all, so the dumper\nends up waiting for a thread that never parks. Refusing the creation\nleaves the cancellation where it is. But it's very ugly to run io_uring\nwork even before we did all the generic exit work."}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["kernel/fork.c"],"versions":[{"version":"92307383082daff5df884a25df9e283efb7ef261","lessThan":"3a0cdf3eb9c3026b046efe32f01b9090ab4e2d73","status":"affected","versionType":"git"},{"version":"92307383082daff5df884a25df9e283efb7ef261","lessThan":"64f2a38a1658493d7a53d656bcc483ee4b837623","status":"affected","versionType":"git"},{"version":"92307383082daff5df884a25df9e283efb7ef261","lessThan":"9dea2e237ffe2a325b9d42ed15ea9ee6561979c7","status":"affected","versionType":"git"},{"version":"92307383082daff5df884a25df9e283efb7ef261","lessThan":"026aa32c00b0b3ea849d0ae98313274c9d3c7e21","status":"affected","versionType":"git"},{"version":"92307383082daff5df884a25df9e283efb7ef261","lessThan":"1f978881ce6c9ac4f4d4a7b6a6e52339eadcd350","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["kernel/fork.c"],"versions":[{"version":"5.16","status":"affected"},{"version":"0","lessThan":"5.16","status":"unaffected","versionType":"semver"},{"version":"6.12.117","lessThanOrEqual":"6.12.*","status":"unaffected","versionType":"semver"},{"version":"6.18.61","lessThanOrEqual":"6.18.*","status":"unaffected","versionType":"semver"},{"version":"7.2.15","lessThanOrEqual":"7.2.*","status":"unaffected","versionType":"semver"},{"version":"7.3.2","lessThanOrEqual":"7.3.*","status":"unaffected","versionType":"semver"},{"version":"7.4-rc1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.16","versionEndExcluding":"6.12.117"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.16","versionEndExcluding":"6.18.61"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.16","versionEndExcluding":"7.2.15"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.16","versionEndExcluding":"7.3.2"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.16","versionEndExcluding":"7.4-rc1"}]}]}],"references":[{"url":"https://git.kernel.org/stable/c/3a0cdf3eb9c3026b046efe32f01b9090ab4e2d73"},{"url":"https://git.kernel.org/stable/c/64f2a38a1658493d7a53d656bcc483ee4b837623"},{"url":"https://git.kernel.org/stable/c/9dea2e237ffe2a325b9d42ed15ea9ee6561979c7"},{"url":"https://git.kernel.org/stable/c/026aa32c00b0b3ea849d0ae98313274c9d3c7e21"},{"url":"https://git.kernel.org/stable/c/1f978881ce6c9ac4f4d4a7b6a6e52339eadcd350"}],"title":"fork: don't create io threads once PF_POSTCOREDUMP is set","x_generator":{"engine":"bippy-1.2.0"}}}}