LoongArch: BPF: Sign extend kfunc call arguments
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:
LoongArch: BPF: Sign extend kfunc call arguments
The kfunc calls are native calls so they should follow LoongArch calling conventions. Sign extend its arguments properly to avoid kernel panic. This is done by adding a new emit_abi_ext() helper. The emit_abi_ext() helper performs extension in place meaning a value already store in the target register (Note: this is different from the existing sign_extend() helper and thus we can't reuse it).
From the CVE record · Linux
The Linux kernel’s LoongArch BPF code does not properly sign-extend kfunc call arguments, which can cause a kernel panic. The input does not specify how an attacker could trigger the issue or whether access, authentication, or user interaction is required.
Engineers running Linux kernels on LoongArch should check whether their kernel includes this fix; affected versions are not specified.