CVE-2026-98378
bpf: Skip unsettled links in link iterator
No known exploitation. EPSS puts it in the 5th percentile. Fixed versions are out.
What to do
Find your product and version, then upgrade to the build on the right.
- LinuxAffected: ≥ 9f88361273082825d9f0d13a543d49f9fa0d44a8, < 68930f8d40ab4c10ca3b019f076136758fd100a8Upgrade to: 68930f8d40ab4c10ca3b019f076136758fd100a8Affected: ≥ 9f88361273082825d9f0d13a543d49f9fa0d44a8, < c251ed48bd9063cf7de6049421e78b6de989060fUpgrade to: c251ed48bd9063cf7de6049421e78b6de989060fAffected: ≥ 9f88361273082825d9f0d13a543d49f9fa0d44a8, < 798a61edbc436cacdb659927d067368eeb1e30e2Upgrade to: 798a61edbc436cacdb659927d067368eeb1e30e2Affected: ≥ 9f88361273082825d9f0d13a543d49f9fa0d44a8, < 6e271f093d15d323f42de26f66556af53fa8e19fUpgrade to: 6e271f093d15d323f42de26f66556af53fa8e19f + 2 more branchesStated by: CVE record
Versions as the sources state them. Full version matrix after sign-in
What it is
From the CVE record
In the Linux kernel, the following vulnerability has been resolved: bpf: Skip unsettled links in link iterator bpf_link_prime() inserts a link into link_idr before anon_inode_getfile() succeeds and before bpf_link_settle() publishes the ID in link->id. bpf_link_by_id() treats such an ID-zero link as unsettled, but the link iterator takes a reference without this check. If anon_inode_getfile() then fails, the creator removes the ID and frees its still-private link directly. The iterator is left with a dangling reference and its next bpf_link_put() accesses freed memory. Treat ID-zero entries as transient in bpf_link_get_curr_or_next(), just as bpf_link_by_id() does. BUG: KASAN: slab-use-after-free in bpf_link_put Write of size 8 by task exp/384 Call Trace: bpf_link_put kernel/bpf/syscall.c:3372 bpf_link_seq_next kernel/bpf/link_iter.c:33 bpf_seq_read kernel/bpf/bpf_iter.c:158 vfs_read fs/read_write.c:572 ksys_read fs/read_write.c:716 do_syscall_64 arch/x86/entry/syscall_64.c:84 entry_SYSCALL_64_after_hwframe arch/x86/entry/entry_64.S:121 Kernel panic - not syncing: KASAN: panic_on_warn set ...
In plain language
No plain-language summary for this CVE yet.
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.2% chance of exploitation activity in the next 30 days, which ranks it in the 5th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
2 events over 0 days, from the signal feeds we watch.
- Publishedrecord updated
Affected products
Sources
References in the record
- git.kernel.org/stable/c/68930f8d40ab4c10ca3b019f076136758fd100a8
- git.kernel.org/stable/c/c251ed48bd9063cf7de6049421e78b6de989060f
- git.kernel.org/stable/c/798a61edbc436cacdb659927d067368eeb1e30e2
And 3 more references. See all after sign-in
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Linux, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI