CVE-2026-98085: bpf: backtrack_insn(): Handle ld_{abs,ind} subprog exit edge
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.20% (FIRST EPSS).
- Fixed version: Linux Linux 12c064bcfa56e3631be9f5336ee113b7f849959a, 19cca7c36055906b3cff3e297618ee8a50cde25d, 387b1baefbb776e3f48dc2261e77a49213f470f7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 12c064bcfa56e3631be9f5336ee113b7f849959a, 19cca7c36055906b3cff3e297618ee8a50cde25d, 387b1baefbb776e3f48dc2261e77a49213f470f7; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.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: 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.
- Published
- Sep 25, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.2% · 10th 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.2%
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
- 928d354ae3557e8f755a227e67be88034eb3cd7f, 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe, de1055e7f9e67af32b1f3376066272b04e5223c0, d846d83bdacbd8f14fc45c63b8c1d22608452e1c, 7.1affected
- 37ad2bb11e9de92cb7b94548705eeedd87f7d392 and later · before 19cca7c36055906b3cff3e297618ee8a50cde25daffected · git
- 8674e2db06cff6b50f2216eed9a761d15425bb34 and later · before 12c064bcfa56e3631be9f5336ee113b7f849959aaffected · git
- ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337 and later · before a0cd9e22f8faed30a8da8be357c51bd8b3074ee9affected · git
- ee861486e377edc55361c08dcbceab3f6b6577bd and later · before 671b7b9a660ef15b25faa3df161205b9dc8d1eb2affected · git
- ee861486e377edc55361c08dcbceab3f6b6577bd and later · before 387b1baefbb776e3f48dc2261e77a49213f470f7affected · git
- 6.6.148 and later · before 6.6.160affected · semver
- 6.12.101 and later · before 6.12.114affected · semver
- 6.18.42 and later · before 6.18.57affected · semver
- 5.10.265 and later · before 5.11affected · 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 | from 0 | — |
| Debian:13 | linux | before 6.12.115-2 | 6.12.115-2 |
| 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-98081Sep 25, 2026 · btrfs: zoned: finish active block group cleanup if call_zone_finish() fails0Monitor
- ← EarlierCVE-2026-98084Sep 25, 2026 · bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks0Monitor
- Later →CVE-2026-98086Sep 25, 2026 · ALSA: ump: do not touch legacy_rmidi before it exists0Monitor
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 | 12c064bcfa56e3631be9f5336ee113b7f849959a | Vendor (CNA) |
| Linux Linux | 19cca7c36055906b3cff3e297618ee8a50cde25d | Vendor (CNA) |
| Linux Linux | 387b1baefbb776e3f48dc2261e77a49213f470f7 | Vendor (CNA) |
| Linux Linux | 5.11 | Vendor (CNA) |
| Linux Linux | 5.16 | Vendor (CNA) |
| Linux Linux | 6.12.114 | Vendor (CNA) |
| Linux Linux | 6.18.57 | Vendor (CNA) |
| Linux Linux | 6.2 | Vendor (CNA) |
| Linux Linux | 6.6.160 | Vendor (CNA) |
| Linux Linux | 671b7b9a660ef15b25faa3df161205b9dc8d1eb2 | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | a0cd9e22f8faed30a8da8be357c51bd8b3074ee9 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.12.115-2 · Debian:13 | Package registry (OSV) |
| debian:linux | 7.2.7-1 · Debian:14 | 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.