CVE-2026-99797

medium

Description

In the Linux kernel, the following vulnerability has been resolved: io_uring/cancel: drop sqd->lock while SQPOLL waits An exiting SQPOLL thread calls io_uring_cancel_generic() with sqd->lock held, and keeps it across cond_resched() and the sleep until nothing is in flight anymore. A zero-copy send notification can't be canceled and stays pending as long as the peer doesn't read, so the lock is held for as long as a user cares to. io_ring_exit_work() needs it to park the thread, and so do IORING_REGISTER_IOWQ_AFF and IOWQ_MAX_WORKERS. With 64 such rings sharing the thread, every iou_exit slot sleeps on the lock and no ring gets freed for anyone. Drop the lock around cond_resched() and the sleep, like the main loop of the thread does. Each walk of ctx_list is still under one hold, and nothing is kept across the unlock. The thread drops its io-wq, frees its tctx and clears sqd->thread under one hold after the loop, so whoever holds the lock and finds sqd->thread set can still use them. [axboe: adapted to the schedule_timeout() based loop]

References

https://git.kernel.org/stable/c/cb0306c52ffae083a86fb283de67875ae7a9500e

https://git.kernel.org/stable/c/9ebfcc60793a46eaf60fc34792486c9a6e114460

https://git.kernel.org/stable/c/96ba960a6099935cfc5ea17aef056553f0c8e647

https://git.kernel.org/stable/c/682a8804640b6266a4b7fae5a131c57dd8711f70

https://euvd.enisa.europa.eu/vulnerability/EUVD-2026-131214

Details

Source: Mitre, NVD

Published: 2026-11-20

Updated: 2026-11-20

Risk Information

CVSS v2

Base Score: 4.9

Vector: CVSS2#AV:L/AC:L/Au:N/C:N/I:N/A:C

Severity: Medium

CVSS v3

Base Score: 5.5

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Severity: Medium

EPSS

EPSS: 0.00296