CVE-2026-98384: bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destroy()
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.15% (FIRST EPSS).
- Fixed version: Linux Linux 01b245ba016d44861690594e10f67e026ce8552f, 2534a5e5d360c2b10203cfa80f4ab9d021e48f2f, 5b4eb82475ae17d55974235c09e97044829426a8; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
Low priority for now. Upgrade to Linux Linux 01b245ba016d44861690594e10f67e026ce8552f, 2534a5e5d360c2b10203cfa80f4ab9d021e48f2f, 5b4eb82475ae17d55974235c09e97044829426a8; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.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 out-of-bounds read of sk_protocol in bpf_sock_destroy() sk_protocol lives in struct sock, not in struct sock_common. A timewait or request sock handed to bpf_sock_destroy() by the tcp iterator is neither, so reading sk->sk_protocol runs past the object: ================================================================== BUG: KASAN: slab-out-of-bounds in bpf_sock_destroy+0xc7/0xe0 Read of size 2 at addr ffff8881047d11b4 by task test_progs/428 Tainted: [W]=WARN Call Trace: <TASK> dump_stack_lvl+0x91/0xf0 print_report+0xd1/0x630 kasan_report+0xf3/0x130 __asan_report_load2_noabort+0x14/0x30 bpf_sock_destroy+0xc7/0xe0 bpf_prog_c3dd61f9d9cd9f37_iter_tcp6_timewait+0x9f/0xb7 bpf_iter_run_prog+0x538/0xde0 bpf_iter_tcp_seq_show+0x26b/0x4b0 bpf_seq_read+0x424/0x1210 vfs_read+0x197/0xe40 ksys_read+0x119/0x240 __x64_sys_read+0x72/0xc0 x64_sys_call+0x647/0x27e0 do_syscall_64+0xe5/0x610 entry_SYSCALL_64_after_hwframe+0x76/0x7e Only check sk_protocol on full socks. tcp_abort() already knows how to deal with TIME_WAIT and NEW_SYN_RECV socks. Also fix the comment, it never matched the code.
- Published
- Oct 9, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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
- 6.5affected
- 4ddbcb886268af8d12a23e6640b39d1d9c652b1b and later · before 5b4eb82475ae17d55974235c09e97044829426a8affected · git
- 4ddbcb886268af8d12a23e6640b39d1d9c652b1b and later · before a9651704c6fd64590b5ad4fbe7c3768accf95993affected · git
- 4ddbcb886268af8d12a23e6640b39d1d9c652b1b and later · before 91a482a81eabddebf5430cbbdf12027e1a91b767affected · git
- 4ddbcb886268af8d12a23e6640b39d1d9c652b1b and later · before 2534a5e5d360c2b10203cfa80f4ab9d021e48f2faffected · git
- 4ddbcb886268af8d12a23e6640b39d1d9c652b1b and later · before 01b245ba016d44861690594e10f67e026ce8552faffected · git
- before 6.5not affected · semver
- 6.6.158 and later · up to and including 6.6.*not affected · semver
- 6.12.112 and later · up to and including 6.12.*not affected · semver
- 6.18.55 and later · up to and including 6.18.*not 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-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-98382Oct 9, 2026 · bpf: Reject dev-bound-only programs on other devices31Monitor
- ← EarlierCVE-2026-98383Oct 9, 2026 · bpf: Disallow bpf_skb_pull_data() for LWT_SEG6LOCAL31Monitor
- Later →CVE-2026-98385Oct 12, 2026 · sched/cache: Decouple sched_cache_group from mm to fix UAF31Monitor
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 | 01b245ba016d44861690594e10f67e026ce8552f | Vendor (CNA) |
| Linux Linux | 2534a5e5d360c2b10203cfa80f4ab9d021e48f2f | Vendor (CNA) |
| Linux Linux | 5b4eb82475ae17d55974235c09e97044829426a8 | Vendor (CNA) |
| Linux Linux | 91a482a81eabddebf5430cbbdf12027e1a91b767 | Vendor (CNA) |
| Linux Linux | a9651704c6fd64590b5ad4fbe7c3768accf95993 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.158.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.113-1 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.9-1 · Debian:14 | 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
- TodayOct 30, 2026+21 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).
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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.