In the Linux kernel, the following vulnerability has been resolved: bpf: Add schedule points in batch ops syzbot reported various soft…
Linux·CWE-834·Published 2024-08-22
In the Linux kernel, the following vulnerability has been resolved: bpf: Add schedule points in batch ops syzbot reported various soft lockups caused by bpf batch operations. INFO: task kworker/1:1:27 blocked for more than 140 seconds. INFO: task hung in rcu_barrier Nothing prevents batch ops to process huge amount of data, we need to add schedule points in them. Note that maybe_wait_bpf_programs(map) calls from generic_map_delete_batch() can be factorized by moving the call after the loop. This will be done later in -next tree once we get this fix merged, unless there is strong opinion doing this optimization sooner.
In the Linux kernel, the following vulnerability has been resolved: bpf: Add schedule points in batch ops syzbot reported various soft lockups caused by bpf batch operations. INFO: task kworker/1:1:27 blocked for more than 140 seconds. INFO: task hung in rcu_barrier Nothing prevents batch ops to process huge amount of data, we need to add schedule points in them. Note that maybe_wait_bpf_programs(map) calls from generic_map_delete_batch() can be factorized by moving the call after the loop. This will be done later in -next tree once we get this fix merged, unless there is strong opinion doing this optimization sooner.
En el kernel de Linux, se resolvió la siguiente vulnerabilidad: bpf: agregar puntos de programación en operaciones por lotes syzbot informó varios bloqueos suaves causados por operaciones por lotes de bpf. INFORMACIÓN: tarea kworker/1:1:27 bloqueada durante más de 140 segundos. INFORMACIÓN: tarea colgada en rcu_barrier Nada impide que las operaciones por lotes procesen una gran cantidad de datos, necesitamos agregar puntos de programación en ellas. Tenga en cuenta que las llamadas de Maybe_wait_bpf_programs(map) desde generic_map_delete_batch() se pueden factorizar moviendo la llamada después del ciclo. Esto se hará más adelante en el árbol siguiente una vez que combinemos esta solución, a menos que haya una opinión firme sobre realizar esta optimización antes.
| Version | Type | Source | Base | Exp | Impact | Vector |
|---|---|---|---|---|---|---|
| 3.1 | Primary | NVD | 3.3 | 1.8 | 1.4 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |