# CVE-2026-98384: bpf: Fix out-of-bounds read of sk_protocol in bpf_sock_destroy()

> A local attacker with low privileges can trigger an out-of-bounds read in the Linux kernel BPF subsystem, potentially causing a crash or leaking memory.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106914, BELL-CVE-2026-98384, DEBIAN-CVE-2026-98384, GHSA-rjxf-mj66-7hpg, UBUNTU-CVE-2026-98384

## What is CVE-2026-98384?

CVE-2026-98384 is a memory corruption vulnerability in Linux, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2026-98384?


## How do I fix CVE-2026-98384?

Apply the vendor's patch.

## Is CVE-2026-98384 being exploited?

There is no known exploitation of CVE-2026-98384 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98384 and fix it if it is affected.

What it is: CVE-2026-98384 is a memory corruption vulnerability in Linux, published on 9 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98384 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98384/ (Markdown: https://insights.sbomify.com/CVE-2026-98384/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98384
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98384
- OSV: https://osv.dev/vulnerability/CVE-2026-98384

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98384/
Summaries are generated and may contain mistakes; the official description above is the record.