CVE-2026-98063: bpf: Fix NULL-ptr-deref in btf_var_show()
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.17% (FIRST EPSS).
- Fixed version: Linux Linux 5403a383f52fc0905703b488f7c3db4b2447dc58, 5756450c9a702da0efb4a993d0a6766b965736f3, aec0a9c1579eb9edf534960be592d09481bd7ac3; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.158.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 5403a383f52fc0905703b488f7c3db4b2447dc58, 5756450c9a702da0efb4a993d0a6766b965736f3, aec0a9c1579eb9edf534960be592d09481bd7ac3; 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 NULL-ptr-deref in btf_var_show() btf_var_show() calls btf_type_id_resolve() unconditionally, which dereferences btf->resolved_ids. That is NULL for a base BTF - e.g. the vmlinux BTF that bpf_snprintf_btf() renders against - since base BTF is not resolved during parsing. btf_modifier_show() guards this with 'if (btf->resolved_ids)', but btf_var_show() does not. A BPF program that passes the type_id of a BTF_KIND_VAR from the vmlinux BTF to bpf_snprintf_btf() thus NULL-derefs: KASAN: probably user-memory-access in range [0x46638-0x4663f] RIP: 0010:btf_var_show (kernel/bpf/btf.c:2929) Call Trace: <TASK> btf_type_show (kernel/bpf/btf.c:8259) btf_type_snprintf_show (kernel/bpf/btf.c:8329) 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:84) entry_SYSCALL_64_after_hwframe (arch/x86/entry/entry_64.S:121) </TASK> Resolve the var's type directly with btf_type_skip_modifiers() when resolved_ids is NULL, mirroring btf_modifier_show().
- Published
- Sep 25, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th 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
- 5.10affected
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before 5756450c9a702da0efb4a993d0a6766b965736f3affected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before e83fcbe3b5d4a1ffb0569bb7c280358065c6017aaffected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before e0d6a06171633d3ee3f7a39b57e5c845fb2b79f2affected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before aec0a9c1579eb9edf534960be592d09481bd7ac3affected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before e472ae0d97865e2021ee668a13eab64013aebf23affected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before ca086264e98108b44fdf53971033811a48defe2baffected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before ea383b3ea56979ce54c8aa88e6ec67164986c401affected · git
- c4d0bfb45068d853a478b9067a95969b1886a30f and later · before 5403a383f52fc0905703b488f7c3db4b2447dc58affected · git
- before 5.10not 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.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-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-98060Sep 25, 2026 · bpf: Reject resilient lock operations in rbtree callbacks0Monitor
- ← EarlierCVE-2026-98061Sep 25, 2026 · bpf: Reject tail calls directly from callback frames0Monitor
- Later →CVE-2026-98064Sep 25, 2026 · bpf: Fix NULL-ptr-deref when showing a void BTF type0Monitor
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 | 5403a383f52fc0905703b488f7c3db4b2447dc58 | Vendor (CNA) |
| Linux Linux | 5756450c9a702da0efb4a993d0a6766b965736f3 | Vendor (CNA) |
| Linux Linux | aec0a9c1579eb9edf534960be592d09481bd7ac3 | Vendor (CNA) |
| Linux Linux | ca086264e98108b44fdf53971033811a48defe2b | Vendor (CNA) |
| Linux Linux | e0d6a06171633d3ee3f7a39b57e5c845fb2b79f2 | Vendor (CNA) |
| Linux Linux | e472ae0d97865e2021ee668a13eab64013aebf23 | Vendor (CNA) |
| Linux Linux | e83fcbe3b5d4a1ffb0569bb7c280358065c6017a | Vendor (CNA) |
| Linux Linux | ea383b3ea56979ce54c8aa88e6ec67164986c401 | 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.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-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.
No dated events beyond publication.
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-1184 · Sep 28, 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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/5756450c9a702da0efb4a993d0a6766b965736f3
- git.kernel.org/stable/c/aec0a9c1579eb9edf534960be592d09481bd7ac3
- git.kernel.org/stable/c/ca086264e98108b44fdf53971033811a48defe2b
- git.kernel.org/stable/c/e0d6a06171633d3ee3f7a39b57e5c845fb2b79f2
- git.kernel.org/stable/c/e472ae0d97865e2021ee668a13eab64013aebf23
- git.kernel.org/stable/c/e83fcbe3b5d4a1ffb0569bb7c280358065c6017a
- git.kernel.org/stable/c/ea383b3ea56979ce54c8aa88e6ec67164986c401
Vendor advisories and official records. Exploit/PoC links are deliberately left out.