From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99799: io_uring/sqpoll: don't wait for the thread to exit
Date: Fri, 20 Nov 2026 08:02:18 +0100 [thread overview]
Message-ID: <2026112017-CVE-2026-99799-4cf1@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
io_uring/sqpoll: don't wait for the thread to exit
io_sq_thread_stop() wakes the SQPOLL thread and waits for it to exit.
The thread belongs to the thread group that created the ring, so a
SIGSTOP or the cgroup freezer holds it in get_signal(), and the wake up
doesn't change that. io_ring_exit_work() then sleeps in that wait until
someone continues or kills the process. iou_exit has 64 slots, so 64
closed SQPOLL rings of a stopped process keep every other ring from
being freed, for everyone.
Don't wait. Set the stop bit, wake the thread, and let it exit when it
gets to run again. The sqd can now outlive its last ring, so give it a
second refcount with one reference for the rings and one for the thread,
and free it with the last one. The thread can't reach a freed ring,
rings leave ctx_list before dropping their reference, and the io-wq hash
is refcounted.
The Linux kernel CVE team has assigned CVE-2026-99799 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.12 with commit 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and fixed in 6.12.117 with commit a85561cc4fc542443c9e3c363f8bcb2c016da68e
Issue introduced in 5.12 with commit 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and fixed in 6.18.61 with commit 8bfd0b6319261f08b29945228b3377f89211f303
Issue introduced in 5.12 with commit 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and fixed in 7.3.2 with commit 8298ce6443ff75f7edc3e30c967270a9c3c12d4b
Issue introduced in 5.12 with commit 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and fixed in 7.4-rc1 with commit 360395e8dbf9d23579f74b84a1af11190813b0f8
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-99799
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
io_uring/sqpoll.c
io_uring/sqpoll.h
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a85561cc4fc542443c9e3c363f8bcb2c016da68e
https://git.kernel.org/stable/c/8bfd0b6319261f08b29945228b3377f89211f303
https://git.kernel.org/stable/c/8298ce6443ff75f7edc3e30c967270a9c3c12d4b
https://git.kernel.org/stable/c/360395e8dbf9d23579f74b84a1af11190813b0f8
reply other threads:[~2026-11-20 7:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026112017-CVE-2026-99799-4cf1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.