bpf: Mask pseudo pointer values in verifier logs
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 4976b718c3551faba2c0616ef55ebeb74db1c5ca · < 72a85e9464a5332fb2cd7efd26d9295275ceda2d| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
bpf: Mask pseudo pointer values in verifier logs
print_bpf_insn() masks ldimm64 immediates for pointer-bearing pseudo sources when pointer leaks are not allowed, but the mask only covers BPF_PSEUDO_MAP_FD and BPF_PSEUDO_MAP_VALUE.
BPF_PSEUDO_MAP_IDX, BPF_PSEUDO_MAP_IDX_VALUE, and BPF_PSEUDO_BTF_ID can also be resolved to kernel pointer values before the verifier log prints the instruction. Include them in the existing pointer classification so the log prints 0x0 instead of the rewritten address.
From the CVE record · Linux
The Linux kernel BPF verifier log can print kernel pointer values for certain pseudo sources even when pointer leaks are not allowed. Someone able to view an affected verifier log could see those addresses; the input does not specify network access, authentication requirements, or user interaction.
Engineers running Linux kernels with BPF verifier logging should check their versions; affected versions are not specified.