| 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-37787: net: dsa: mv88e6xxx: avoid unregistering devlink regions which were never registered |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| net: dsa: mv88e6xxx: avoid unregistering devlink regions which were never registered |
| |
| Russell King reports that a system with mv88e6xxx dereferences a NULL |
| pointer when unbinding this driver: |
| https://lore.kernel.org/netdev/Z_lRkMlTJ1KQ0kVX@shell.armlinux.org.uk/ |
| |
| The crash seems to be in devlink_region_destroy(), which is not NULL |
| tolerant but is given a NULL devlink global region pointer. |
| |
| At least on some chips, some devlink regions are conditionally registered |
| since the blamed commit, see mv88e6xxx_setup_devlink_regions_global(): |
| |
| if (cond && !cond(chip)) |
| continue; |
| |
| These are MV88E6XXX_REGION_STU and MV88E6XXX_REGION_PVT. If the chip |
| does not have an STU or PVT, it should crash like this. |
| |
| To fix the issue, avoid unregistering those regions which are NULL, i.e. |
| were skipped at mv88e6xxx_setup_devlink_regions_global() time. |
| |
| The Linux kernel CVE team has assigned CVE-2025-37787 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 5.15.181 with commit 8ccdf5e24b276848eefb2755e05ff0f005a0c4a1 |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 6.1.135 with commit b3c70dfe51f10df60db2646c08cebd24bcdc5247 |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 6.6.88 with commit bbb80f004f7a90c3dcaacc982c59967457254a05 |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 6.12.25 with commit 3665695e3572239dc233216f06b41f40cc771889 |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 6.14.4 with commit 5f5e95945bb1e08be7655da6acba648274db457d |
| Issue introduced in 5.13 with commit 836021a2d0e0e4c90b895a35bd9c0342071855fb and fixed in 6.15 with commit c84f6ce918a9e6f4996597cbc62536bbf2247c96 |
| |
| 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-37787 |
| 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: |
| drivers/net/dsa/mv88e6xxx/devlink.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/8ccdf5e24b276848eefb2755e05ff0f005a0c4a1 |
| https://git.kernel.org/stable/c/b3c70dfe51f10df60db2646c08cebd24bcdc5247 |
| https://git.kernel.org/stable/c/bbb80f004f7a90c3dcaacc982c59967457254a05 |
| https://git.kernel.org/stable/c/3665695e3572239dc233216f06b41f40cc771889 |
| https://git.kernel.org/stable/c/5f5e95945bb1e08be7655da6acba648274db457d |
| https://git.kernel.org/stable/c/c84f6ce918a9e6f4996597cbc62536bbf2247c96 |
