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-98084bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks When processing calls to bpf_loop() verifier marks R1 (and R4) as precise. R1 tracks loop iterations number and because of the 'callback_depth < R1' mechanics in check_helper_call() must be marked precise. However, precision propagation for R1 was broken, when bpf_loop() call was verified on a second iteration. Consider the following verification trace: - main: bpf_loop(nr_loops, callback ...) - callback: BPF_EXIT - main: bpf_loop(nr_loops, callback ...) - ... While the first visit of the call to bpf_loop() propagated R1 precision as expected, the second call to mark_chain_precision() in the check_helper_call() set R1, but it was immediately reset when backtrack_insn() processed preceding BPF_EXIT in the loop deleted in this patch. Because of that, the second visit of the call to bpf_loop() injected checkpoint with R1 not marked as precise. Which could trick the verifier into accepting unsafe programs. See the next patch for an example of such program. Commit is structured in a way to minimize conflicts when 'bpf' would be eventually merged with 'bpf-next'.

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.17% · top 94% of all CVEs (16 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 b43550d7d58e7ae6618aaab18c1e912fa4d6e3dd – < 1ac58dab0a83d2c64e3b807a3a0b399f17a74110
    • affected ab5cfac139ab8576fb54630d4cca23c3e690ee90 – < cdc93c6370f792d0649df2a145ac0cdcd430e411
    • affected ab5cfac139ab8576fb54630d4cca23c3e690ee90 – < 3a39bc9707fbd1bef4df7318a9d02222741dda5b
    • affected ab5cfac139ab8576fb54630d4cca23c3e690ee90 – < f83890dfed9efc5e19df1dbc1ad707a142936923
    • affected ab5cfac139ab8576fb54630d4cca23c3e690ee90 – < e3e4f66cc4b72333d0886ae2673c360248987889
    • affected 6.6.15 – < 6.6.160
  • Linux · Linux

    • affected 6.7
    • unaffected < 6.7
    • 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-98084 badge
[![CVE-2026-98084](https://cveledger.app/badge/CVE-2026-98084.svg)](https://cveledger.app/cve/CVE-2026-98084)

Record last updated .