bpf: Fix stackmap overflow check on 32-bit arches
- 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 4.19.311, 5.4.273, 5.10.214, 4.10, 4.15, and 5 more
- 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: bpf: Fix stackmap overflow check on 32-bit arches The stackmap code relies on roundup_pow_of_two() to compute the number of hash buckets, and contains an overflow check by checking if the resulting value is 0. However, on 32-bit arches, the roundup code itself can overflow by doing a 32-bit left-shift of an unsigned long value, which is undefined behaviour, so it is not guaranteed to truncate neatly. This was triggered by syzbot on the DEVMAP_HASH type, which contains the same check, copied from the hashtab code. The commit in the fixes tag actually attempted to fix this, but the fix did not account for the UB, so the fix only works on CPUs where an overflow does result in a neat truncation to zero, which is not guaranteed. Checking the value before rounding does not have this problem.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 063c722dd9d285d877e6fd499e753d6224f4c046 · fixed in d0e214acc59145ce25113f617311aa79dda39cb3; From 7e3a6b820535eb395784060ae26c5af579528fa0 · fixed in 21e5fa4688e1a4d3db6b72216231b24232f75c1d; From 8032bf2af9ce26b3a362b9711d15f626ab946a74 · fixed in 15641007df0f0d35fa28742b25c2a7db9dcd6895; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in ca1f06e72dec41ae4f76e7b1a8a97265447b46ae; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in f06899582ccee09bd85d0696290e3eaca9aa042d; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in 7070b274c7866a4c5036f8d54fcaf315c64ac33a; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in 43f798b9036491fb014b55dd61c4c5c3193267d0; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in 0971126c8164abe2004b8536b49690a0d6005b0a; From 6183f4d3a0a2ad230511987c6c362ca43ec0055f · fixed in 7a4b21250bf79eef26543d35bd390448646c536b; From 4.19.177 · fixed in 4.19.311; From 5.4.99 · fixed in 5.4.273; From 5.10.17 · fixed in 5.10.214; From 4.9.258 · fixed in 4.10; From 4.14.222 · fixed in 4.15
- Linux Linux
5.11
- KernelLinux
fixed in 4.19.311; From 4.20.0 · fixed in 5.4.273; From 5.5.0 · fixed in 5.10.214; From 5.11.0 · fixed in 5.15.153; fixed in 6.1.83; From 5.16.0 · fixed in 6.6.23; From 6.2.0 · fixed in 6.7.11; From 6.7.0 · fixed in 6.8.2
References 9
git.kernel.org
- stable/c/d0e214acc59145ce25113f617311aa79dda39cb3
- stable/c/21e5fa4688e1a4d3db6b72216231b24232f75c1d
- stable/c/15641007df0f0d35fa28742b25c2a7db9dcd6895
- stable/c/ca1f06e72dec41ae4f76e7b1a8a97265447b46ae
- stable/c/f06899582ccee09bd85d0696290e3eaca9aa042d
- stable/c/7070b274c7866a4c5036f8d54fcaf315c64ac33a
- stable/c/43f798b9036491fb014b55dd61c4c5c3193267d0
- stable/c/0971126c8164abe2004b8536b49690a0d6005b0a
- stable/c/7a4b21250bf79eef26543d35bd390448646c536b