UNKNOWNCVSS not yet scoredVulnerability

CVE-2026-99797

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]

Properties

Last source
FIRST EPSS
Nvd fetched at
2026-11-22T12:30:49.958423+00:00
Epss score
0.00296
Cve id
CVE-2026-99797
First seen by Signal
2026-11-20T11:40:59+00:00
Name
CVE-2026-99797
Retrieved at
2026-11-22T12:32:29+00:00
Published at
2026-11-20T08:18:37.297
Last modified
2026-11-20T08:18:37.297
Epss percentile
0.22624

Related research

Explore deeper with Ninja Signal's threat intelligence graph

CVE-2026-99797 — Ninja Signal Threat Intelligence | Ninja Signal