CVE-2026-99801: Linux kernel · io_uring/bpf-ops: clear bpf_ctx while submitting SQEs
Affects Linux kernelSource CVE Database V5
Not known to be exploited : upgrade to 521861b17a107875c884df9474e7746617f256d5 or 8543a39f03db8816a2d80d0c92c132a19f2afb48 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 521861b17a107875c884df9474e7746617f256d5, 8543a39f03db8816a2d80d0c92c132a19f2afb48
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 521861b17a107875c884df9474e7746617f256d5 or 8543a39f03db8816a2d80d0c92c132a19f2afb48.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
AI-suggested
A fix has been implemented in the Linux kernel by clearing the BPF context while submitting SQEs. Users should update to the fixed kernel versions identified by commits 521861b17a107875c884df9474e7746617f256d5 and 8543a39f03db8816a2d80d0c92c132a19f2afb48 to remediate this vulnerability.
Description
A vulnerability in the Linux kernel's io_uring subsystem related to BPF operations was fixed by clearing the BPF context while submitting submission queue entries (SQEs). The flaw allowed tasks without proper capabilities to perform socket operations such as setting SO_MARK, IP_TRANSPARENT, or TCP_REPAIR without holding necessary locks, potentially leading to race conditions and double free errors. The issue was addressed by clearing the run context around io_submit_sqes(), ensuring SQEs from userspace are issued safely.