CVE-2026-99796Linux
NVD
Vulnerability Summary
In the Linux kernel, the following vulnerability has been resolved:
io_uring/poll: cancel all matching requests in one pass
With IORING_ASYNC_CANCEL_ALL, __io_async_cancel() calls io_try_cancel()
until nothing is found, and io_poll_cancel() cancels one request per
call, starting each lookup at the beginning of the hash. A cancelled
request stays hashed until its task work runs, so every lookup walks
past the ones already cancelled. Cancelling K of N pending polls visits
about K*N/2 requests in one io_uring_enter(), with uring_lock held.
A single CANCEL_FD|ALL on 80000 polls on one eventfd takes 17.06s,
0.02s with this change. With voluntary preemption the soft lockup
watchdog fires:
watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [repro:100]
RIP: 0010:io_cancel_req_match+0x19/0xa0
io_poll_cancel+0x73/0x170
io_try_cancel+0x7b/0xf0
__io_async_cancel+0x41/0x110
Walk the hash once and cancel every match, as io_cancel_remove() does
for futex and waitid. Cancel by user_data only needs its own bucket.
__io_async_cancel() still loops until nothing is found, so a request
that io-wq parks in the poll hash meanwhile is still cancelled.
A cancel that matches one request now walks the whole hash twice instead
of stopping at the match.
io_uring/poll: cancel all matching requests in one pass
With IORING_ASYNC_CANCEL_ALL, __io_async_cancel() calls io_try_cancel()
until nothing is found, and io_poll_cancel() cancels one request per
call, starting each lookup at the beginning of the hash. A cancelled
request stays hashed until its task work runs, so every lookup walks
past the ones already cancelled. Cancelling K of N pending polls visits
about K*N/2 requests in one io_uring_enter(), with uring_lock held.
A single CANCEL_FD|ALL on 80000 polls on one eventfd takes 17.06s,
0.02s with this change. With voluntary preemption the soft lockup
watchdog fires:
watchdog: BUG: soft lockup - CPU#1 stuck for 26s! [repro:100]
RIP: 0010:io_cancel_req_match+0x19/0xa0
io_poll_cancel+0x73/0x170
io_try_cancel+0x7b/0xf0
__io_async_cancel+0x41/0x110
Walk the hash once and cancel every match, as io_cancel_remove() does
for futex and waitid. Cancel by user_data only needs its own bucket.
__io_async_cancel() still loops until nothing is found, so a request
that io-wq parks in the poll hash meanwhile is still cancelled.
A cancel that matches one request now walks the whole hash twice instead
of stopping at the match.
Affected & Patched Versions
- Linux >= 8e29da69feade64ec7fe9e1a2824b967c5183a21 and < 9073da4d5bd87c71235d909512c478e8a13a5818
- Linux >= 8e29da69feade64ec7fe9e1a2824b967c5183a21 and < 5310b477e619209b0cceb00b71ebc05a3e89360b
- Linux >= 8e29da69feade64ec7fe9e1a2824b967c5183a21 and < e409e1b03059c544d271c7f8e1215c5c0c62f278
- Linux >= 8e29da69feade64ec7fe9e1a2824b967c5183a21 and < 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480
- Linux 5.19
- Linux 9073da4d5bd87c71235d909512c478e8a13a5818
- Linux 5310b477e619209b0cceb00b71ebc05a3e89360b
- Linux e409e1b03059c544d271c7f8e1215c5c0c62f278
- Linux 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480
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-99796. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alertsExternal References
- Referencehttps://git.kernel.org/stable/c/5310b477e619209b0cceb00b71ebc05a3e89360b
- Referencehttps://git.kernel.org/stable/c/9073da4d5bd87c71235d909512c478e8a13a5818
- Referencehttps://git.kernel.org/stable/c/9eff9c07e927dcd9c57150cd6fb3d4ec76f00480
- Referencehttps://git.kernel.org/stable/c/e409e1b03059c544d271c7f8e1215c5c0c62f278
Data last checked: Nov 22, 2026 12:25 UTC