bpf: backtracking shouldn't clear outer frame R1-R5 for callbacks
- 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.6.160, 6.12.114, 6.18.57, 7.2.7
- 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
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'.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From b43550d7d58e7ae6618aaab18c1e912fa4d6e3dd · fixed in 1ac58dab0a83d2c64e3b807a3a0b399f17a74110; From ab5cfac139ab8576fb54630d4cca23c3e690ee90 · fixed in cdc93c6370f792d0649df2a145ac0cdcd430e411; From ab5cfac139ab8576fb54630d4cca23c3e690ee90 · fixed in 3a39bc9707fbd1bef4df7318a9d02222741dda5b; From ab5cfac139ab8576fb54630d4cca23c3e690ee90 · fixed in f83890dfed9efc5e19df1dbc1ad707a142936923; From ab5cfac139ab8576fb54630d4cca23c3e690ee90 · fixed in e3e4f66cc4b72333d0886ae2673c360248987889; From 6.6.15 · fixed in 6.6.160
- Linux Linux
6.7
- KernelLinux
fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; fixed in 6.18.57; From 6.13.0 · fixed in 7.2.7