bpf: Mark signal tracepoint siginfo arguments as scalar
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:
bpf: Mark signal tracepoint siginfo arguments as scalar
The signal_generate and signal_deliver tracepoints declare their info argument as a struct kernel_siginfo pointer. btf_ctx_access() therefore treats it as a trusted pointer for tp_btf programs.
Signal delivery also uses SEND_SIG_NOINFO and SEND_SIG_PRIV as special values for this argument. Those values are zero and one respectively, and are not pointers. A tp_btf program can currently dereference either value and fault the kernel. In particular, signal_generate can run from timer interrupt context, turning the fault into a kernel panic.
Record both tracepoints in raw_tp_null_args[] and mark argument one as a non-pointer. This preserves scalar access to the cookie while rejecting direct and helper-mediated pointer use. Merely marking it nullable would not suffice because SEND_SIG_PRIV is nonzero.
From the CVE record · Linux
The Linux kernel treats the info argument of the signal_generate and signal_deliver tracepoints as a trusted pointer, although it can contain special non-pointer values. A tp_btf program that dereferences one of those values can fault the kernel; if signal_generate runs in timer interrupt context, the fault can cause a kernel panic. The input does not specify authentication or user-interaction requirements.
Engineers running Linux kernels that expose these BPF signal tracepoints should check whether their kernel includes the fix; affected versions are not specified.