In the Linux kernel, the following vulnerability has been resolved:net_sched: sch_sfq: move the limit validationIt is not sufficient to directly validate the limit on the data thatthe user passes as it can be updated based on how the other parametersare changed.Move the check at the end of the configuration update process to alsocatch scenarios where the limit is indirectly updated, for examplewith the following configurations:tc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 depth 1tc qdisc add dev dummy0 handle 1: root sfq limit 2 flows 1 divisor 1This fixes the following syzkaller reported crash:------------[ cut here ]------------UBSAN: array-index-out-of-bounds in net/sched/sch_sfq.c:203:6index 65535 is out of range for type 'struct sfq_head[128]'CPU: 1 UID: 0 PID: 3037 Comm: syz.2.16 Not tainted 6.14.0-rc2-syzkaller #0Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 12/27/2024Call Trace:
No PoCs from references.
- https://github.com/0xor0ne/awesome-list
- https://github.com/ARPSyndicate/cve-scores
- https://github.com/w4zu/Debian_security
- https://github.com/xairy/linux-kernel-exploitation