CVE-2024-26885

bpf: Fix DEVMAP_HASH overflow check on 32-bit arches

HIGH
7.8
CVSS Score
Published: April 17, 2024 at 10:27 AM UTC
Updated: October 15, 2026 at 01:17 AM UTC
2 products affected across 2 vendorsLinux KernelSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: bpf: Fix DEVMAP_HASH overflow check on 32-bit arches The devmap code allocates a number hash buckets equal to the next power of two of the max_entries value provided when creating the map. When rounding up to the next power of two, the 32-bit variable storing the number of buckets can overflow, and the code checks for overflow by checking if the truncated 32-bit value is equal to 0. However, on 32-bit arches the rounding up itself can overflow mid-way through, because it ends up doing a left-shift of 32 bits on an unsigned long value. If the size of an unsigned long is four bytes, this is undefined behaviour, so there is no guarantee that we'll end up with a nice and tidy 0-value at the end. Syzbot managed to turn this into a crash on arm32 by creating a DEVMAP_HASH with max_entries > 0x80000000 and then trying to update it. Fix this by moving the overflow check to before the rounding up operation.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.11 ≤ v < 5.15.1535.16 ≤ v < 6.1.835.4 ≤ v < 5.10.2146.2 ≤ v < 6.6.236.7 ≤ v < 6.7.116.8 ≤ v < 6.8.25.46f9d451ab1a36f9d451ab1a33728adb72d7ff66a7b374d665176
Vendor states this is fixed in 1f5e352b9088211fa5eb4e1639cd365f4f7d2f65 (fixed)
Vendor states this is fixed in 22079b3a423382335f47d9ed32114e6c9fe88d7c (fixed)
Vendor states this is fixed in 250051acc21f9d4c5c595e4fcb55986ea08c4691 (fixed)
Vendor states this is fixed in 281d464a34f540de166cee74b723e97ac2515ec3 (fixed)
Vendor states this is fixed in 4b81a9f92b3676cb74b907a7a209b3d15bd9a7f9 (fixed)
Vendor states this is fixed in c826502bed93970f2fd488918a7b8d5f1d30e2e3 (fixed)
Vendor states this is fixed in e89386f62ce9a9ab9a94835a9890883c23d9d52c (fixed)
Vendor states this is fixed in edf7990baa48de5097daa9ac02e06cb4c798a737 (fixed)
Affected range stops below 5.10.214, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 5.10.227 (unaffected)
Vendor states this is fixed in 5.15.153 (unaffected)
Vendor states this is fixed in 5.4 (unaffected)
Vendor states this is fixed in 5.4.285 (unaffected)
Vendor states this is fixed in 6.1.83 (unaffected)
Vendor states this is fixed in 6.6.23 (unaffected)
Vendor states this is fixed in 6.7.11 (unaffected)
Vendor states this is fixed in 6.8.2 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (11)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHLinux
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-119

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card