bpf: Fix bpf_sock context code generation
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ c3c16f2ea6d20159903cf93afbb1155f3d8348d5 · < d95dd5a6c6cd08d5ae466d3aed27b3cf59155a6c| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Fix bpf_sock context code generation
Currently, the ctx access code reads the rx_queue_mapping field with either a 4-byte or 2-byte load. The rest of the bits in the register are marked known zero by the verifier. However, the emitted ctx access code places in the register on certain the special value (-1) using BPF_MOV_IMM64, which gets sign-extended to turn on all the bits in the register. By shifting this value right, the program ends up with a value at runtime above what the verifier assumes is possible.
Fix this by ensuring the read value is as wide as the assumed size. Use MOV32 instructions instead of MOV64 instructions to keep the upper bits zero as assumed by the verifier. Also properly report the size of the destination variable (the bpf_sock field, 4 bytes) instead of the source (the socket field, 2 bytes).
From the CVE record · Linux
The Linux kernel’s bpf_sock context code can place a value in a register that exceeds what the BPF verifier assumes is possible. A program can then obtain an unexpected value by shifting that register. The input does not specify an attack path, authentication requirements, or user interaction.
Engineers running Linux kernels with the affected bpf_sock context code should check their versions; no affected version range is provided.