CVE-2026-99799Linux
NVD
Vulnerability Summary
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.
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.
Affected & Patched Versions
- Linux >= 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and < a85561cc4fc542443c9e3c363f8bcb2c016da68e
- Linux >= 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and < 8bfd0b6319261f08b29945228b3377f89211f303
- Linux >= 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and < 8298ce6443ff75f7edc3e30c967270a9c3c12d4b
- Linux >= 16efa4fce3b7af17bb45d635c3e89992d721e0f3 and < 360395e8dbf9d23579f74b84a1af11190813b0f8
- Linux 5.12
- Linux a85561cc4fc542443c9e3c363f8bcb2c016da68e
- Linux 8bfd0b6319261f08b29945228b3377f89211f303
- Linux 8298ce6443ff75f7edc3e30c967270a9c3c12d4b
- Linux 360395e8dbf9d23579f74b84a1af11190813b0f8
What to do
Fix it during your normal patch cycle. No exploitation is confirmed yet.
- Check whether you run Linux and which version.
- Update to a patched version listed above, then confirm the new version.
Timeline
- Nov 20, 2026Published
- Nov 20, 2026Record last modified
Score, severity and exploitation changes are tracked from the day Watchtower started logging them.
Get notified about new Linux CVEsYou are reading CVE-2026-99799. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://git.kernel.org/stable/c/360395e8dbf9d23579f74b84a1af11190813b0f8
- Referencehttps://git.kernel.org/stable/c/8298ce6443ff75f7edc3e30c967270a9c3c12d4b
- Referencehttps://git.kernel.org/stable/c/8bfd0b6319261f08b29945228b3377f89211f303
- Referencehttps://git.kernel.org/stable/c/a85561cc4fc542443c9e3c363f8bcb2c016da68e
Data last checked: Nov 22, 2026 12:25 UTC