CVE-2026-98590bpf: Fix bpf_sock context code generation
- —Not scoredno CVSS score yet
- 0.22%Exploitation in 30 daysEPSS · top 88% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix bpf_sock context code generation Currently, the ctx access code reads the rx_queue_mapping field with either a 4-byte or 2-byte load. The rest of the bits in the register are marked known zero by the verifier. However, the emitted ctx access code places in the register on certain the special value (-1) using BPF_MOV_IMM64, which gets sign-extended to turn on all the bits in the register. By shifting this value right, the program ends up with a value at runtime above what the verifier assumes is possible. Fix this by ensuring the read value is as wide as the assumed size. Use MOV32 instructions instead of MOV64 instructions to keep the upper bits zero as assumed by the verifier. Also properly report the size of the destination variable (the bpf_sock field, 4 bytes) instead of the source (the socket field, 2 bytes).
Timeline
ID reserved
By Linux
- 23 days later
· 23 days later
Published
- 1 day later
· 1 day later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.22% · top 88% of all CVEs (18 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < e3ddcf4aeb342d4de2e5761c7042270d454752de
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < 4a41d064facc3330e176ecbbf5b0026ed18a5c69
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < 70288599d1754e157df8326239316dbdf08ea33c
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < ea4dc96c902ccfa49dd3e4f23c443dab4a74b018
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < 84ebb991ae985149079ae9ab51b7e3ba25a9ff53
- affected c3c16f2ea6d20159903cf93afbb1155f3d8348d5 – < 4a4852376e3a2727ea40e61143d6d7c22bb6dfad
- affected 5.8
- unaffected < 5.8
- unaffected 5.10.271 – ≤ 5.10.*
- unaffected 5.15.222 – ≤ 5.15.*
- unaffected 6.1.189 – ≤ 6.1.*
- unaffected 6.6.158 – ≤ 6.6.*
- unaffected 6.12.112 – ≤ 6.12.*
- unaffected 6.18.55 – ≤ 6.18.*
- unaffected 7.2.9 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References8
- https://git.kernel.org/stable/c/e3ddcf4aeb342d4de2e5761c7042270d454752de (opens in a new tab)
- https://git.kernel.org/stable/c/4a41d064facc3330e176ecbbf5b0026ed18a5c69 (opens in a new tab)
- https://git.kernel.org/stable/c/70288599d1754e157df8326239316dbdf08ea33c (opens in a new tab)
- https://git.kernel.org/stable/c/ea4dc96c902ccfa49dd3e4f23c443dab4a74b018 (opens in a new tab)
- https://git.kernel.org/stable/c/b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73 (opens in a new tab)
- https://git.kernel.org/stable/c/d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c (opens in a new tab)
- https://git.kernel.org/stable/c/84ebb991ae985149079ae9ab51b7e3ba25a9ff53 (opens in a new tab)
- https://git.kernel.org/stable/c/4a4852376e3a2727ea40e61143d6d7c22bb6dfad (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-103635 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-98590)Record last updated .