Answer in brief
CVE-2026-98064 records a Unknown severity vulnerability in bpf: Fix NULL-ptr-deref when showing a void BTF type. 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 | >=c4d0bfb45068d853a478b9067a95969b1886a30f <717abdfd1d559d01fdd102023f0a990fb0437240 || >=c4d0bfb45068d853a478b9067a95969b1886a30f <98f1cb95221332139acf514350ae2cae3b8656c5 || >=c4d0bfb45068d853a478b9067a95969b1886a30f <5324f4e75ff6e9c2ca2e267c5f34f0937f9d0ac9 || >=c4d0bfb45068d853a478b9067a95969b1886a30f <4ea508b9ebd78bce7f212166d2e2cba66b875f08 | 717abdfd1d559d01fdd102023f0a990fb0437240, 98f1cb95221332139acf514350ae2cae3b8656c5, 5324f4e75ff6e9c2ca2e267c5f34f0937f9d0ac9, 4ea508b9ebd78bce7f212166d2e2cba66b875f08 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 25, 2026
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix NULL-ptr-deref when showing a void BTF type btf_modifier_show() resolves the modifier and then calls btf_type_ops(t)->show() unconditionally. For the void type (type_id 0, BTF_KIND_UNKN) kind_ops[] has no entry, so ->show is NULL. A "const void" (a modifier resolving to void) cannot be a map key or value - map_check_btf() rejects it because void has no size - so the map dump path does not reach it. But bpf_snprintf_btf() takes a type_id straight from the BPF program, and passing such a "const void" from the vmlinux BTF NULL-derefs: KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] RIP: 0010:btf_modifier_show (kernel/bpf/btf.c:2914) Call Trace: <TASK> btf_type_show (kernel/bpf/btf.c:8251) btf_type_snprintf_show (kernel/bpf/btf.c:8321) bpf_snprintf_btf (kernel/trace/bpf_trace.c:1047) bpf_prog_test_run_raw_tp (net/bpf/test_run.c:829) __sys_bpf (kernel/bpf/syscall.c:4804) do_syscall_64 (arch/x86/entry/syscall_64.c:94) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Fall back to btf_df_show() when the resolved type has no show op; it emits the "<unsupported kind:N>" placeholder already used for kinds like FWD and FUNC. bpf_snprintf_btf() then returns the length as usual.
Quoted source text, attributed separately from HOL analysis.