| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025052618-CVE-2025-37992-1590@gregkh> Date: Mon, 26 May 2025 16:54:19 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-37992: net_sched: Flush gso_skb list too during ->change() From: Greg Kroah-Hartman <gregkh@...nel.org> Description =========== In the Linux kernel, the following vulnerability has been resolved: net_sched: Flush gso_skb list too during ->change() Previously, when reducing a qdisc's limit via the ->change() operation, only the main skb queue was trimmed, potentially leaving packets in the gso_skb list. This could result in NULL pointer dereference when we only check sch->limit against sch->q.qlen. This patch introduces a new helper, qdisc_dequeue_internal(), which ensures both the gso_skb list and the main queue are properly flushed when trimming excess packets. All relevant qdiscs (codel, fq, fq_codel, fq_pie, hhf, pie) are updated to use this helper in their ->change() routines. The Linux kernel CVE team has assigned CVE-2025-37992 to this issue. Affected and fixed versions =========================== Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 5.15.184 with commit d3336f746f196c6a53e0480923ae93939f047b6c Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 6.1.140 with commit d38939ebe0d992d581acb6885c1723fa83c1fb2c Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 6.6.92 with commit a7d6e0ac0a8861f6b1027488062251a8e28150fd Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 6.12.30 with commit d1365ca80b012d8a7863e45949e413fb61fa4861 Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 6.14.8 with commit fe88c7e4fc2c1cd75a278a15ffbf1689efad4e76 Issue introduced in 3.5 with commit 76e3cc126bb223013a6b9a0e2a51238d1ef2e409 and fixed in 6.15 with commit 2d3cbfd6d54a2c39ce3244f33f85c595844bd7b8 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-37992 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: include/net/sch_generic.h net/sched/sch_codel.c net/sched/sch_fq.c net/sched/sch_fq_codel.c net/sched/sch_fq_pie.c net/sched/sch_hhf.c net/sched/sch_pie.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/d3336f746f196c6a53e0480923ae93939f047b6c https://git.kernel.org/stable/c/d38939ebe0d992d581acb6885c1723fa83c1fb2c https://git.kernel.org/stable/c/a7d6e0ac0a8861f6b1027488062251a8e28150fd https://git.kernel.org/stable/c/d1365ca80b012d8a7863e45949e413fb61fa4861 https://git.kernel.org/stable/c/fe88c7e4fc2c1cd75a278a15ffbf1689efad4e76 https://git.kernel.org/stable/c/2d3cbfd6d54a2c39ce3244f33f85c595844bd7b8
Powered by blists - more mailing lists