CVE-2026-99796
Severity unknownNo known exploitationFix availableio_uring/poll: cancel all matching requests in one pass
Record last updated
CVSS score
No score published yet
EPSS, chance of exploitation in 30 days
Higher than 23% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
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.
Patching and mitigation
- Patch status
- Fix available (source: CVE record (Linux))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- No vendor link on record
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Linux | Linux | from 8e29da69feade64ec7fe9e1a2824b967c5183a21 before 5310b477e619209b0cceb00b71ebc05a3e89360b | 5310b477e619209b0cceb00b71ebc05a3e89360b | CVE Program |
| Linux | Linux | from 8e29da69feade64ec7fe9e1a2824b967c5183a21 before e409e1b03059c544d271c7f8e1215c5c0c62f278 | e409e1b03059c544d271c7f8e1215c5c0c62f278 | CVE Program |
| Linux | Linux | from 8e29da69feade64ec7fe9e1a2824b967c5183a21 before 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480 | 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480 | CVE Program |
| Linux | Linux | from 8e29da69feade64ec7fe9e1a2824b967c5183a21 before 9073da4d5bd87c71235d909512c478e8a13a5818 | 9073da4d5bd87c71235d909512c478e8a13a5818 | CVE Program |
| Linux | Linux | 5.19 | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.12.118 up to and including 6.12.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 6.18.64 up to and including 6.18.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | from 7.3.5 up to and including 7.3.* | Not documented | CVE Program |
| Linux | Linux (unaffected) | 7.4-rc2 | Not documented | CVE Program |
| Linux | Linux (unaffected) | all versions before 5.19 | Not documented | CVE Program |
Timeline
Disclosure
CVE record published by Linux
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (Linux)
Vendor guidance and references
- https://git.kernel.org/stable/c/5310b477e619209b0cceb00b71ebc05a3e89360b (opens in a new tab)
- https://git.kernel.org/stable/c/9073da4d5bd87c71235d909512c478e8a13a5818 (opens in a new tab)
- https://git.kernel.org/stable/c/9eff9c07e927dcd9c57150cd6fb3d4ec76f00480 (opens in a new tab)
- https://git.kernel.org/stable/c/e409e1b03059c544d271c7f8e1215c5c0c62f278 (opens in a new tab)