| From bippy-1.2.0 Mon Sep 17 00:00:00 2001 |
| From: Greg Kroah-Hartman <gregkh@kernel.org> |
| To: <linux-cve-announce@vger.kernel.org> |
| Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org> |
| Subject: CVE-2025-37914: net_sched: ets: Fix double list add in class with netem as child qdisc |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net_sched: ets: Fix double list add in class with netem as child qdisc |
| |
| As described in Gerrard's report [1], there are use cases where a netem |
| child qdisc will make the parent qdisc's enqueue callback reentrant. |
| In the case of ets, there won't be a UAF, but the code will add the same |
| classifier to the list twice, which will cause memory corruption. |
| |
| In addition to checking for qlen being zero, this patch checks whether |
| the class was already added to the active_list (cl_is_active) before |
| doing the addition to cater for the reentrant case. |
| |
| [1] https://lore.kernel.org/netdev/CAHcdcOm+03OD2j6R0=YHKqmy=VgJ8xEOKuP6c7mSgnp-TEJJbw@mail.gmail.com/ |
| |
| The Linux kernel CVE team has assigned CVE-2025-37914 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 5.10.238 with commit 24388ba0a1b1b6d4af1b205927ac7f7b119ee4ea |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 5.15.182 with commit 554acc5a2ea9703e08023eb9a003f9e5a830a502 |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 6.1.138 with commit 9efb6a0fa88e0910d079fdfeb4f7ce4d4ac6c990 |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 6.6.90 with commit 72c3da7e6ceb74e74ddbb5a305a35c9fdfcac6e3 |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 6.12.28 with commit 1f01e9f961605eb397c6ecd1d7b0233dfbf9077c |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 6.14.6 with commit bc321f714de693aae06e3786f88df2975376d996 |
| Issue introduced in 5.6 with commit dcc68b4d8084e1ac9af0d4022d6b1aff6a139a33 and fixed in 6.15 with commit 1a6d0c00fa07972384b0c308c72db091d49988b6 |
| |
| 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-37914 |
| 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: |
| net/sched/sch_ets.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/24388ba0a1b1b6d4af1b205927ac7f7b119ee4ea |
| https://git.kernel.org/stable/c/554acc5a2ea9703e08023eb9a003f9e5a830a502 |
| https://git.kernel.org/stable/c/9efb6a0fa88e0910d079fdfeb4f7ce4d4ac6c990 |
| https://git.kernel.org/stable/c/72c3da7e6ceb74e74ddbb5a305a35c9fdfcac6e3 |
| https://git.kernel.org/stable/c/1f01e9f961605eb397c6ecd1d7b0233dfbf9077c |
| https://git.kernel.org/stable/c/bc321f714de693aae06e3786f88df2975376d996 |
| https://git.kernel.org/stable/c/1a6d0c00fa07972384b0c308c72db091d49988b6 |
