bpf: Copy per-CPU map value padding in copy_map_value_long()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 448325199f574d33824dbf9121efb03558412966 · < 7cf9cd98cf6f0df3befc167ca6b54c07014d71de| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Copy per-CPU map value padding in copy_map_value_long()
In kernel, per-CPU map elements are stored with round_up(map->value_size, 8) bytes. On UAPI lookup paths, it copies the rounded size for each CPU into a temporary buffer.
However, copy_map_value_long() passes 'map->value_size' to bpf_obj_memcpy(). When the map has special fields, bpf_obj_memcpy() copies around those fields with memcpy(), and does not copy the tail padding between 'map->value_size' and round_up(map->value_size, 8).
The temporary UAPI lookup buffers are allocated without __GFP_ZERO. As a result, when the per-CPU map's value size is not equal to round_up(map->value_size, 8), UAPI LOOKUP_ELEM and its variants can return stale heap contents from that padding to user space. The same issue applies to bpf_iter for per-CPU maps.
Pass round_up(map->value_size, 8) to bpf_obj_memcpy() from copy_map_value_long(), so per-CPU maps both with and without special fields copy the entire per-CPU slot. Remove the now redundant round_up() from bpf_obj_memcpy()'s long_memcpy path.
From the CVE record · Linux
Linux kernel BPF per-CPU map lookups can expose stale heap contents in padding returned to user space. This occurs when a map has special fields and its value size is not a multiple of eight; the issue also affects bpf_iter for per-CPU maps. Exploitation requires access to the affected lookup or iterator path; the input does not specify authentication requirements or user interaction.
Operators running Linux kernels with BPF per-CPU maps should check their kernel vendor's advisory; affected versions were not provided.