CVE-2026-98590: bpf: Fix bpf_sock context code generation
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 4a41d064facc3330e176ecbbf5b0026ed18a5c69, 4a4852376e3a2727ea40e61143d6d7c22bb6dfad, 70288599d1754e157df8326239316dbdf08ea33c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 4a41d064facc3330e176ecbbf5b0026ed18a5c69, 4a4852376e3a2727ea40e61143d6d7c22bb6dfad, 70288599d1754e157df8326239316dbdf08ea33c; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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).
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.8affected
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before e3ddcf4aeb342d4de2e5761c7042270d454752deaffected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before 4a41d064facc3330e176ecbbf5b0026ed18a5c69affected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before 70288599d1754e157df8326239316dbdf08ea33caffected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before ea4dc96c902ccfa49dd3e4f23c443dab4a74b018affected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73affected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6caffected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before 84ebb991ae985149079ae9ab51b7e3ba25a9ff53affected · git
- c3c16f2ea6d20159903cf93afbb1155f3d8348d5 and later · before 4a4852376e3a2727ea40e61143d6d7c22bb6dfadaffected · git
- before 5.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98588Oct 18, 2026 · bpf, sockmap: Reject max_entries > INT_MAX in sock_map_alloc0Monitor
- ← EarlierCVE-2026-98589Oct 18, 2026 · bpf: Reject pkt arguments in mutating subprogs0Monitor
- Later →CVE-2026-98591Oct 18, 2026 · bpf: Fix bounds check for skb-backed dynptrs0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 4a41d064facc3330e176ecbbf5b0026ed18a5c69 | Vendor (CNA) |
| Linux Linux | 4a4852376e3a2727ea40e61143d6d7c22bb6dfad | Vendor (CNA) |
| Linux Linux | 70288599d1754e157df8326239316dbdf08ea33c | Vendor (CNA) |
| Linux Linux | 84ebb991ae985149079ae9ab51b7e3ba25a9ff53 | Vendor (CNA) |
| Linux Linux | b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73 | Vendor (CNA) |
| Linux Linux | d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c | Vendor (CNA) |
| Linux Linux | e3ddcf4aeb342d4de2e5761c7042270d454752de | Vendor (CNA) |
| Linux Linux | ea4dc96c902ccfa49dd3e4f23c443dab4a74b018 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 12, 2026+25 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/4a4852376e3a2727ea40e61143d6d7c22bb6dfad
- git.kernel.org/stable/c/70288599d1754e157df8326239316dbdf08ea33c
- git.kernel.org/stable/c/84ebb991ae985149079ae9ab51b7e3ba25a9ff53
- git.kernel.org/stable/c/b3f37afc7fd7c52bc2114310aff1eb24c7cd4d73
- git.kernel.org/stable/c/d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c
- git.kernel.org/stable/c/e3ddcf4aeb342d4de2e5761c7042270d454752de
- git.kernel.org/stable/c/ea4dc96c902ccfa49dd3e4f23c443dab4a74b018
Vendor advisories and official records. Exploit/PoC links are deliberately left out.