Kernel panic via unsettled link reference
Published Oct 9, 2026 · Updated Oct 9, 2026
Use-after-free in the Linux BPF link iterator allows local users to crash the kernel by racing link creation with iteration. The bpf_link_get_curr_or_next() function references an ID-zero link before creation finishes; if anon_inode_getfile() fails, creation cleanup frees that link and the iterator later accesses freed memory in bpf_link_put(). Triggering requires access to BPF link iteration and concurrent failed link creation; the reported panic occurred with KASAN panic_on_warn enabled, and the record does not establish privilege escalation.
Summary
What happened
Use-after-free in the Linux BPF link iterator allows local users to crash the kernel by racing link creation with iteration. The bpf_link_get_curr_or_next() function references an ID-zero link before creation finishes; if anon_inode_getfile() fails, creation cleanup frees that link and the iterator later accesses freed memory in bpf_link_put(). Triggering requires access to BPF link iteration and concurrent failed link creation; the reported panic occurred with KASAN panic_on_warn enabled, and the record does not establish privilege escalation.
The record
- CVE
- CVE-2026-98378
- Published
- Oct 9, 2026
- Updated
- Oct 9, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Oct 9, 2026CVE publishedPublication date reported by the CVE source.
- Oct 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.19
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <50e80e2bb5e2be8515205b9c496b9640ddefa434
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <68930f8d40ab4c10ca3b019f076136758fd100a8
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <6e271f093d15d323f42de26f66556af53fa8e19f
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <798a61edbc436cacdb659927d067368eeb1e30e2
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <87ce4b53b7436b50fc984f0a6afaf77f68ac5573
- Affected versionversion=9f88361273082825d9f0d13a543d49f9fa0d44a8 <c251ed48bd9063cf7de6049421e78b6de989060f
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started