PT-2026-151772
CVE-2026-99561
·
Published
2026-11-19
·
Updated
2026-11-19
Description by
Score
N/A
Not availableNo severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
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.
Found an issue in the description? Have something to add? Feel free to write us 👾