riscv, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
riscv, bpf: Fix missing sign-ext for signed 1-byte and 2-byte kfunc args
On RV64, the ABI requires sign-extension for signed 1-byte and 2-byte kfunc args. However, the RV64 JIT currently does not perform sign-extension for such kfunc args.
Before commit 7ce090afbf72 ("bpf: Infer zext_dst based on static register liveness analysis"), state pruning could potentially omit zero-extension of 32-bit subregisters, which inadvertently masked the above issue by making the args appear as if they had been properly sign-extended. After that commit, the problem is exposed, causing the kfunc_call/kfunc_call_test4 selftest to fail.
Fix this by extending the existing sign-extension logic to handle signed 1-byte and 2-byte kfunc args as well.
From the CVE record · Linux
On RV64, the Linux kernel BPF JIT does not sign-extend signed 1-byte and 2-byte kfunc arguments as the ABI requires. This can cause the kfunc_call/kfunc_call_test4 selftest to fail; the input does not describe an attacker outcome, access requirements, or user interaction.
Engineers running Linux kernels on RV64 should check whether their kernel includes the RISC-V BPF JIT fix; affected versions are not specified.