In the Linux kernel, the following vulnerability has been resolved:
bpf: Avoid __bpf_prog_ret0_warn when jit fails
syzkaller reported an issue:
WARNING: CPU: 3 PID: 217 at kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357
Modules linked in:
CPU: 3 UID: 0 PID: 217 Comm: kworker/u32:6 Not tainted 6.15.0-rc4-syzkaller-00040-g8bac8898fe39
RIP: 0010:__bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357
Call Trace:
<TASK>
bpf_dispatcher_nop_func include/linux/bpf.h:1316 [inline]
__bpf_prog_run include/linux/filter.h:718 [inline]
bpf_prog_run include/linux/filter.h:725 [inline]
cls_bpf_classify+0x74a/0x1110 net/sched/cls_bpf.c:105
...
When creating bpf program, 'fp->jit_requested' depends on bpf_jit_enable.
This issue is triggered because of CONFIG_BPF_JIT_ALWAYS_ON is not set
and bpf_jit_enable is set to 1, causing the arch to attempt JIT the prog,
but jit failed due to FAULT_INJECTION. As a result, incorrectly
treats the program as valid, when the program runs it calls
`__bpf_prog_ret0_warn` and triggers the WARN_ON_ONCE(1).
Additional Descriptions (1)
En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: bpf: evitar __bpf_prog_ret0_warn cuando falla jit syzkaller informó un problema: ADVERTENCIA: CPU: 3 PID: 217 en kernel/bpf/core.c:2357 __bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Módulos vinculados: CPU: 3 UID: 0 PID: 217 Comm: kworker/u32:6 No contaminado 6.15.0-rc4-syzkaller-00040-g8bac8898fe39 RIP: 0010:__bpf_prog_ret0_warn+0xa/0x20 kernel/bpf/core.c:2357 Rastreo de llamadas: bpf_dispatcher_nop_func include/linux/bpf.h:1316 [en línea] __bpf_prog_run include/linux/filter.h:718 [en línea] bpf_prog_run include/linux/filter.h:725 [en línea] cls_bpf_classify+0x74a/0x1110 net/sched/cls_bpf.c:105 ... Al crear un programa bpf, 'fp->jit_requested' depende de bpf_jit_enable. Este problema se produce porque CONFIG_BPF_JIT_ALWAYS_ON no está configurado y bpf_jit_enable está configurado en 1, lo que provoca que la arquitectura intente ejecutar el programa JIT, pero el JIT falla debido a FAULT_INJECTION. Como resultado, trata incorrectamente el programa como válido, cuando el programa se ejecuta llama a `__bpf_prog_ret0_warn` y activa WARN_ON_ONCE(1).