bpf: Fix linked reg delta tracking when src_reg == dst_reg
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.105, 6.18.33, 7.0.10
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix linked reg delta tracking when src_reg == dst_reg Consider the case of rX += rX where src_reg and dst_reg are pointers to the same bpf_reg_state in adjust_reg_min_max_vals(). The latter first modifies the dst_reg in-place, and later in the delta tracking, the subsequent is_reg_const(src_reg)/reg_const_value(src_reg) reads the post-{add,sub} value instead of the original source. This is problematic since it sets an incorrect delta, which sync_linked_regs() then propagates to linked registers, thus creating a verifier-vs-runtime mismatch. Fix it by just skipping this corner case.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 98d7ca374ba4b39e7535613d40e159f09ca14da2 · fixed in 1509c1ae9185ec7103899967ed788b6eebab3fcc; From 98d7ca374ba4b39e7535613d40e159f09ca14da2 · fixed in d88e8e4a3b52bd5b2ff3eceba4b29d1b5506d066; From 98d7ca374ba4b39e7535613d40e159f09ca14da2 · fixed in cc86a8b0a1c54d2bccf6f68cf49b82dea91b84de; From 98d7ca374ba4b39e7535613d40e159f09ca14da2 · fixed in d7f14173c0d5866c3cae759dee560ad1bed10d2e
- Linux Linux
6.11
- KernelLinux
From 6.11.0 · fixed in 6.12.105; From 6.13.0 · fixed in 6.18.33; From 6.19.0 · fixed in 7.0.10