CVE-2026-98085

bpf: backtrack_insn(): Handle ld_{abs,ind} subprog exit edge

N/A
Published: September 25, 2026 at 10:24 AM UTC
Updated: October 21, 2026 at 01:21 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: backtrack_insn(): Handle ld_{abs,ind} subprog exit edge Nicholas Carlini reported a bug in precision backtracking mechanism for BPF_LD | BPF_{IND,ABS} instructions. These instructions are modelled as two branches: - fallthrough; - implicit exit from current subprogram. The implicit exit case was not handled by the backtrack_insn() function. When backtracking such a path backtrack_insn() did not call bt_subprog_enter(), which meant that backtracking continued manipulating precision marks in a caller frame, while looking at instructions in a callee frame. This lead to segmentation faults during verification (see the selftest), or unsound state pruning.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

37ad2bb11e9de92cb7b94548705eeedd87f7d3925.10.2655.15.2166.1.1836.12.1016.18.426.6.1487.0.107.18674e2db06cff6b50f2216eed9a761d15425bb348a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe928d354ae3557e8f755a227e67be88034eb3cd7fce01a4e5cfac7adbe0be565f90cd32ecbb2f8337d846d83bdacbd8f14fc45c63b8c1d22608452e1cde1055e7f9e67af32b1f3376066272b04e5223c0ee861486e377edc55361c08dcbceab3f6b6577bd
Vendor states this is fixed in 387b1baefbb776e3f48dc2261e77a49213f470f7 (fixed)
Vendor states this is fixed in 671b7b9a660ef15b25faa3df161205b9dc8d1eb2 (fixed)
Affected range stops below 5.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.16, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.12.114 (unaffected)
Affected range stops below 6.13, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.18.57 (unaffected)
Affected range stops below 6.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.2, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.1 (unaffected)
Vendor states this is fixed in 7.2.7 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusUNDERGOING ANALYSIS

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card