Technical impact
The kernel code that manages io_uring cancellation can cause a task to spin when it cannot run pending work. By creating a disabled ring, moving it to another thread, and exiting while a request remains in flight, the exiting thread never sleeps, consumes CPU until the helper thread runs or dies, and when panic_on_warn is enabled the kernel will panic. The outcome is a local denial of service that exhausts CPU resources or crashes the system.
Affected Systems
This flaw affects all Linux kernel builds that include the io_uring subsystem prior to the patch committed by commit 3005459e0ddfcef0f555b6e81f672f2c49a1c0aa. Any Linux system where unprivileged users can instantiate io_uring rings is potentially vulnerable.
Risk and Exploitability
The vulnerability is local and requires a user with permission to create io_uring instances, which is typically granted to all users. The CVSS score of 5.5 indicates medium severity, and the EPSS score is less than 1%, so exploitation is low probability. The KEV catalog does not list this CVE, and because the issue involves a busy loop that can lead to a kernel panic, any exploitation attempt can exhaust CPU resources or crash the system. A vulnerable system cannot tolerate such an event.
Debian DLA