CVE-2026-99799: io_uring/sqpoll: don't wait for the thread to exit

Published Nov 20, 2026
·
Updated

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

iouring/sqpoll: don't wait for the thread to exit

iosqthreadstop() 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 getsignal(), and the wake up doesn't change that. ioringexitwork() then sleeps in that wait until someone continues or kills the process. iouexit 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 ctxlist before dropping their reference, and the io-wq hash is refcounted.

Affected Software

7 affected componentsFixes available
linux/kernel>=5.12.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2
debian/linux*
debian/linux<6.12.117-1
6.12.117-1
debian/linux<7.3.3-1
7.3.3-1
debian/linux<=6.1.176-1, <=6.1.192-2, <=6.12.107-1
6.12.117-17.3.4-17.3.5-1

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.3.2
  4. Upgrade

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

    Fixed in 6.12.117-1
  5. Upgrade

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

    Fixed in 7.3.3-1
  6. Upgrade

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

    Fixed in 6.12.117-1Fixed in 7.3.4-1Fixed in 7.3.5-1

Frequently Asked Questions

1

Who is realistically exposed to this issue?

Systems using io_uring rings configured for SQPOLL are exposed. The impact is broader than the process that created the ring: enough affected closed rings from a stopped process can prevent other io_uring rings from being freed system-wide.

2

What conditions are needed to trigger the resource blockage?

A process must create SQPOLL rings and then be stopped with SIGSTOP or held by the cgroup freezer while its SQPOLL thread is in get_signal(). Closing 64 such rings can fill the 64 io_uring exit-work slots and block freeing of other rings until the stopped process is continued or killed.

3

What can be done if the fix cannot be applied immediately?

Avoid using SQPOLL for rings created by processes that may be stopped or frozen. If the condition has already occurred, continue or kill the stopped or frozen process so its SQPOLL thread can run and exit.

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