CVE-2026-99796: Linux kernel · io_uring/poll: cancel all matching requests in one pass
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e409e1b03059c544d271c7f8e1215c5c0c62f278 : patch Linux kernel soon.
Data as of 20 Nov 2026, 07:21 UTC
Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in e409e1b03059c544d271c7f8e1215c5c0c62f278, 9073da4d5bd87c71235d909512c478e8a13a5818, 5310b477e619209b0cceb00b71ebc05a3e89360b +1
Exploitation evidence
Disclosed: evidence found.
CVE published 20 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade Linux kernel to e409e1b03059c544d271c7f8e1215c5c0c62f278, 9073da4d5bd87c71235d909512c478e8a13a5818, 5310b477e619209b0cceb00b71ebc05a3e89360b or 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix is available in the Linux kernel versions identified by the fixed commit hashes (e409e1b03059c544d271c7f8e1215c5c0c62f278, 9073da4d5bd87c71235d909512c478e8a13a5818, 5310b477e619209b0cceb00b71ebc05a3e89360b, 9eff9c07e927dcd9c57150cd6fb3d4ec76f00480). Users should update to a kernel version including these fixes to resolve the issue. No other mitigation is indicated.
Description
A performance issue in the Linux kernel's io_uring polling cancellation mechanism was fixed. The vulnerability involved inefficient cancellation of multiple matching requests, causing excessive CPU usage and potential soft lockups. The fix optimizes cancellation by walking the hash once and cancelling all matches in one pass, significantly reducing cancellation time and preventing CPU soft lockups.
References
- git.kernel.org/stable/c/9073da4d5bd87c71235d909512c478e8a13a5818 (opens in a new tab)
- git.kernel.org/stable/c/5310b477e619209b0cceb00b71ebc05a3e89360b (opens in a new tab)
- git.kernel.org/stable/c/e409e1b03059c544d271c7f8e1215c5c0c62f278 (opens in a new tab)
- git.kernel.org/stable/c/9eff9c07e927dcd9c57150cd6fb3d4ec76f00480 (opens in a new tab)