bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ eb1f7f71c126c8fd50ea81af98f97c4b581ea4ae · < 2aaf67f0516fde29620d0edfc29c01b9ea7ad430| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Reject rdonly/rdwr_buf_size kfunc arguments that exceed u32 max
check_kfunc_args() detects a kfunc argument named rdonly_buf_size or rdwr_buf_size and stores reg->var_off.value into meta->r0_size, a u64, and does not bound it. check_kfunc_call() later copies that value into the returned register's mem_size field:
meta->r0_size = reg->var_off.value; ... regs[BPF_REG_0].mem_size = meta.r0_size;
regs[BPF_REG_0].mem_size is u32. A constant whose upper 32 bits are set gets truncated instead of causing a load-time rejection, so the verifier records a PTR_TO_MEM register with an approximately 4 GiB mem_size for whatever allocation the kfunc returned. A later access check against that register uses the truncated, wrong bound.
Reject rdonly_buf_size/rdwr_buf_size values that exceed U32_MAX at the point meta->r0_size is set.
From the CVE record · Linux
The Linux kernel BPF verifier does not reject oversized rdonly_buf_size or rdwr_buf_size kfunc arguments before storing them in a 32-bit memory-size field. When a BPF program with such an argument is loaded, truncation can make the verifier use an incorrect bound for later memory-access checks. The input does not specify the privileges required to load the program.
Engineers running Linux kernels with the affected BPF verifier code should check their deployments; affected versions are not specified.