CVE-2026-98590: Linux kernel · bpf: Fix bpf_sock context code generation
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ea4dc96c902ccfa49dd3e4f23c443dab4a74b018 : update Linux kernel when convenient.
Data as of 26 Oct 2026, 12:55 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in ea4dc96c902ccfa49dd3e4f23c443dab4a74b018, e3ddcf4aeb342d4de2e5761c7042270d454752de, d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c +5
Exploitation evidence
Disclosed: evidence found.
CVE published 18 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
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
|
| LinuxLinux | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in multiple Linux kernel commits as listed in the established facts. Users should update to a Linux kernel version that includes these fixes to remediate the vulnerability.
Description
A vulnerability in the Linux kernel's BPF sock context code generation was fixed. The issue involved incorrect handling of the rx_queue_mapping field, where the code used 64-bit moves that caused sign extension and resulted in runtime values exceeding verifier assumptions. The fix ensures proper use of 32-bit move instructions and correct size reporting for the bpf_sock field.
References
- git.kernel.org/stable/c/e3ddcf4aeb342d4de2e5761c7042270d454752de (opens in a new tab)
- git.kernel.org/stable/c/4a41d064facc3330e176ecbbf5b0026ed18a5c69 (opens in a new tab)
- git.kernel.org/stable/c/70288599d1754e157df8326239316dbdf08ea33c (opens in a new tab)
- git.kernel.org/stable/c/ea4dc96c902ccfa49dd3e4f23c443dab4a74b018 (opens in a new tab)
- git.kernel.org/stable/c/b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73 (opens in a new tab)
- git.kernel.org/stable/c/d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c (opens in a new tab)
- git.kernel.org/stable/c/84ebb991ae985149079ae9ab51b7e3ba25a9ff53 (opens in a new tab)
- git.kernel.org/stable/c/4a4852376e3a2727ea40e61143d6d7c22bb6dfad (opens in a new tab)