CVE-2026-99229

io_uring/wait: don't spin on a stuck overflow list

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/wait: don't spin on a stuck overflow list As long as IO_CHECK_CQ_OVERFLOW_BIT is set, io_cqring_wait_schedule() returns right away, before it gets to look at signals or arms the timeout, for io_cqring_wait() to flush the overflow list. If that doesn't empty the list, and the CQ ring doesn't hold the number of events the caller wants, the loop starts over, with the same result. The task spins in the kernel, and can't be killed. The assumption is that this can't happen: if CQEs can't be flushed, the ring is full, and min_events is capped to the size of the ring. But: - With IORING_SETUP_CQE_MIXED a 32b CQE needs two contiguous entries. It is stuck on the list if a single one is free, and then the ring holds less than cq_entries events. A single threaded application that asks for as many events as the ring has entries never gets out of io_uring_enter(). - Whether the ring is full is up to the CQ head, which the application can write to. While one thread waits for events on an empty ring, another one can move the head back so that the ring looks full and have a CQE overflow. The waiter can't be stopped any more, not even by SIGKILL. Only the application can make room in the CQ ring. Return to it if the list could not be flushed.

Key facts

Published
2 Nov 2026
Last changed
6 Nov 2026
Assigned by
Linux
EPSS
0.161% likely to be exploited in the next 30 days, higher than 5.331% of CVEs (scores for 16 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding bf1d2ed84b3162e3b0e0bb7018ac59147da6e975 (affected)
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding a6cfc85c6bf9498aaf1978b503f9663635a1aa22 (affected)
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding 4a89352edd8b3e20d1e1fb33f0fc297dd137149f (affected)
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding c347691e5dc5481b2d6943c123619e04847fb0dc (affected)
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding 340944e27b4bb218ed0ee66d0947ac70faefa05a (affected)
  • 3fcf19d592d5cb63eb209400b22055651e3c27d0 up to but excluding 34f5a664c34d3cb62f6bec7f4156754594a7d25b (affected)
LinuxLinux
  • Default status: affected
  • 6.3 (affected)
  • 0 up to but excluding 6.3 (unaffected)
  • 6.6.161 up to and including 6.6.* (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.60 up to and including 6.18.* (unaffected)
  • 7.2.14 up to and including 7.2.* (unaffected)
  • 7.3.2 up to and including 7.3.* (unaffected)
  • 7.4-rc1 up to and including * (unaffected)

Timeline

  1. 2 Nov 2026 Published

References