CVE-2026-99797Linux
NVD
Vulnerability Summary
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]
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]
Affected & Patched Versions
- Linux >= 63809137ebb58f0aa2ce359117422686e3304f45 and < 9ebfcc60793a46eaf60fc34792486c9a6e114460
- Linux >= 63809137ebb58f0aa2ce359117422686e3304f45 and < 96ba960a6099935cfc5ea17aef056553f0c8e647
- Linux >= 63809137ebb58f0aa2ce359117422686e3304f45 and < 682a8804640b6266a4b7fae5a131c57dd8711f70
- Linux >= 63809137ebb58f0aa2ce359117422686e3304f45 and < cb0306c52ffae083a86fb283de67875ae7a9500e
- Linux 6.0
- Linux 9ebfcc60793a46eaf60fc34792486c9a6e114460
- Linux 96ba960a6099935cfc5ea17aef056553f0c8e647
- Linux 682a8804640b6266a4b7fae5a131c57dd8711f70
- Linux cb0306c52ffae083a86fb283de67875ae7a9500e
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-99797. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://git.kernel.org/stable/c/682a8804640b6266a4b7fae5a131c57dd8711f70
- Referencehttps://git.kernel.org/stable/c/96ba960a6099935cfc5ea17aef056553f0c8e647
- Referencehttps://git.kernel.org/stable/c/9ebfcc60793a46eaf60fc34792486c9a6e114460
- Referencehttps://git.kernel.org/stable/c/cb0306c52ffae083a86fb283de67875ae7a9500e
Data last checked: Nov 22, 2026 12:25 UTC