Answer in brief
CVE-2026-98384 records a Unknown severity vulnerability in bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destroy(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=4ddbcb886268af8d12a23e6640b39d1d9c652b1b <5b4eb82475ae17d55974235c09e97044829426a8 || >=4ddbcb886268af8d12a23e6640b39d1d9c652b1b <a9651704c6fd64590b5ad4fbe7c3768accf95993 || >=4ddbcb886268af8d12a23e6640b39d1d9c652b1b <91a482a81eabddebf5430cbbdf12027e1a91b767 || >=4ddbcb886268af8d12a23e6640b39d1d9c652b1b <2534a5e5d360c2b10203cfa80f4ab9d021e48f2f || >=4ddbcb886268af8d12a23e6640b39d1d9c652b1b <01b245ba016d44861690594e10f67e026ce8552f | 5b4eb82475ae17d55974235c09e97044829426a8, a9651704c6fd64590b5ad4fbe7c3768accf95993, 91a482a81eabddebf5430cbbdf12027e1a91b767, 2534a5e5d360c2b10203cfa80f4ab9d021e48f2f, 01b245ba016d44861690594e10f67e026ce8552f |
| Linux/Linuxgeneric | 6.5 | Not reported |
Published upstream
Oct 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 19, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 9, 2026
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.
Quoted source text, attributed separately from HOL analysis.