Skip to main content
VulnerabilityPublished Updated

CVE-2026-98084: Linux kernel · bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-98084· High

Not known to be exploited · CVSS 5.5 High · fixed in f83890dfed9efc5e19df1dbc1ad707a142936923 : patch Linux kernel soon.

Data as of 17 Nov 2026, 22:49 UTC

CVSS 3.1 base score
5.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in f83890dfed9efc5e19df1dbc1ad707a142936923, e3e4f66cc4b72333d0886ae2673c360248987889, cdc93c6370f792d0649df2a145ac0cdcd430e411 +3
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=6.6.15 <6.6.160
Fixed in
  • f83890dfed9efc5e19df1dbc1ad707a142936923
  • e3e4f66cc4b72333d0886ae2673c360248987889
  • cdc93c6370f792d0649df2a145ac0cdcd430e411
  • 6.6.160
  • 3a39bc9707fbd1bef4df7318a9d02222741dda5b
  • 1ac58dab0a83d2c64e3b807a3a0b399f17a74110
LinuxLinuxAffected
  • =6.7
Fixed in–

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

References

Community reviews

Loading reviews…