CVE-2026-98084

bpf: 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'.

Key facts

Published
25 Sep 2026
Last changed
21 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.086% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • b43550d7d58e7ae6618aaab18c1e912fa4d6e3dd up to but excluding 1ac58dab0a83d2c64e3b807a3a0b399f17a74110 (affected)
  • ab5cfac139ab8576fb54630d4cca23c3e690ee90 up to but excluding cdc93c6370f792d0649df2a145ac0cdcd430e411 (affected)
  • ab5cfac139ab8576fb54630d4cca23c3e690ee90 up to but excluding 3a39bc9707fbd1bef4df7318a9d02222741dda5b (affected)
  • ab5cfac139ab8576fb54630d4cca23c3e690ee90 up to but excluding f83890dfed9efc5e19df1dbc1ad707a142936923 (affected)
  • ab5cfac139ab8576fb54630d4cca23c3e690ee90 up to but excluding e3e4f66cc4b72333d0886ae2673c360248987889 (affected)
  • 6.6.15 up to but excluding 6.6.160 (affected)
LinuxLinux
  • Default status: affected
  • 6.7 (affected)
  • 0 up to but excluding 6.7 (unaffected)
  • 6.6.160 up to and including 6.6.* (unaffected)
  • 6.12.114 up to and including 6.12.* (unaffected)
  • 6.18.57 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References