bpf: Fix DEVMAP_HASH overflow check on 32-bit arches
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 6f9d451ab1a33728adb72d7ff66a7b374d665176 · < 22079b3a423382335f47d9ed32114e6c9fe88d7c| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
On 32-bit architectures, the Linux kernel's BPF DEVMAP_HASH overflow check can fail when a map is created with a very large max_entries value. An actor able to create and update such a map can trigger a kernel crash; the input does not specify authentication requirements or user interaction.
Engineers running the Linux kernel on 32-bit architectures should check their affected versions; no version range is provided.