Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-98085bpf: backtrack_insn(): Handle ld_{abs,ind} subprog exit edge

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Undergoing Analysis.

EPSS (exploitation in 30 days)
0.20% · top 90% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 37ad2bb11e9de92cb7b94548705eeedd87f7d392 – < 19cca7c36055906b3cff3e297618ee8a50cde25d
    • affected 8674e2db06cff6b50f2216eed9a761d15425bb34 – < 12c064bcfa56e3631be9f5336ee113b7f849959a
    • affected ce01a4e5cfac7adbe0be565f90cd32ecbb2f8337 – < a0cd9e22f8faed30a8da8be357c51bd8b3074ee9
    • affected ee861486e377edc55361c08dcbceab3f6b6577bd – < 671b7b9a660ef15b25faa3df161205b9dc8d1eb2
    • affected ee861486e377edc55361c08dcbceab3f6b6577bd – < 387b1baefbb776e3f48dc2261e77a49213f470f7
    • affected 928d354ae3557e8f755a227e67be88034eb3cd7f
    • affected 8a800497d9f6c2ec9c2c1ba7b71d0ac2ea7f7bbe
    • affected de1055e7f9e67af32b1f3376066272b04e5223c0
    • affected d846d83bdacbd8f14fc45c63b8c1d22608452e1c
    • affected 6.6.148 – < 6.6.160
    • affected 6.12.101 – < 6.12.114
    • affected 6.18.42 – < 6.18.57
    • affected 5.10.265 – < 5.11
    • affected 5.15.216 – < 5.16
    • affected 6.1.183 – < 6.2
    • affected 7.0.10 – < 7.1
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-98085 badge
[![CVE-2026-98085](https://cveledger.app/badge/CVE-2026-98085.svg)](https://cveledger.app/cve/CVE-2026-98085)

Record last updated .