CVE-2026-98084 json
bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks
published last mo. modified 21d ago also EUVD-2026-86914
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 6%
- public exploits
- 0
- none known
Summary
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'.
Patch / fix
- Linux Linux 6.6.160, 6.12.114, 6.18.57, 7.2.7, 7.3
- linux Debian 13 6.12.115-2
- linux Debian 14 7.2.7-1
debian advisories DEBIAN-CVE-2026-98084
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-ibm Ubuntu 26.04 LTS 7.0.0-1017.17
- linux-riscv Ubuntu 26.04 LTS 7.0.0-42.42.1
- linux-oracle Ubuntu 26.04 LTS 7.0.0-1015.16
- linux-hwe-7.0 Ubuntu 24.04 LTS 7.0.0-42.42~24.04.1
- linux-oem-7.0 Ubuntu 26.04 LTS 7.0.0-1017.17
ubuntu advisories UBUNTU-CVE-2026-98084
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.9-1.1
opensuse advisories openSUSE-SU-2026:12074-1
- git.kernel.org/stable/c/1ac58dab0a83d2c64e3b807a3a0b399f17a74110 commit
- git.kernel.org/stable/c/cdc93c6370f792d0649df2a145ac0cdcd430e411 commit
- git.kernel.org/stable/c/3a39bc9707fbd1bef4df7318a9d02222741dda5b commit
- git.kernel.org/stable/c/f83890dfed9efc5e19df1dbc1ad707a142936923 commit
- git.kernel.org/stable/c/e3e4f66cc4b72333d0886ae2673c360248987889 commit
Is CVE-2026-98084 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-98084 updated cvss 5.5
kernel: bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9not affected: vulnerable code not present
+1 more productsfewer
Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-11).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/1ac58dab0a83d2c64e3b807a3a0b399f17a74110
- git.kernel.org /stable/c/cdc93c6370f792d0649df2a145ac0cdcd430e411
- git.kernel.org /stable/c/3a39bc9707fbd1bef4df7318a9d02222741dda5b
- git.kernel.org /stable/c/f83890dfed9efc5e19df1dbc1ad707a142936923
- git.kernel.org /stable/c/e3e4f66cc4b72333d0886ae2673c360248987889
Sources
- CVE List CVE-2026-98084
- NVD CVE-2026-98084
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.