[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025090401-CVE-2025-38725-eb3f@gregkh>
Date: Thu, 4 Sep 2025 17:33:30 +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-38725: net: usb: asix_devices: add phy_mask for ax88772 mdio bus
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
net: usb: asix_devices: add phy_mask for ax88772 mdio bus
Without setting phy_mask for ax88772 mdio bus, current driver may create
at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f.
DLink DUB-E100 H/W Ver B1 is such a device. However, only one main phy
device will bind to net phy driver. This is creating issue during system
suspend/resume since phy_polling_mode() in phy_state_machine() will
directly deference member of phydev->drv for non-main phy devices. Then
NULL pointer dereference issue will occur. Due to only external phy or
internal phy is necessary, add phy_mask for ax88772 mdio bus to workarnoud
the issue.
The Linux kernel CVE team has assigned CVE-2025-38725 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 5.15.190 with commit 75947d3200de98a9ded9ad8972e02f1a177097fe
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.1.149 with commit 59ed6fbdb1bc03316e09493ffde7066f031c7524
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.6.103 with commit ccef5ee4adf56472aa26bdd1f821a6d0cd06089a
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.12.43 with commit ee2cd40b0bb46056949a2319084a729d95389386
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.15.11 with commit a754ab53993b1585132e871c5d811167ad3c52ff
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.16.2 with commit ad1f8313aeec0115f9978bd2d002ef4a8d96c773
Issue introduced in 5.14 with commit e532a096be0e5e570b383e71d4560e7f04384e0f and fixed in 6.17-rc2 with commit 4faff70959d51078f9ee8372f8cff0d7045e4114
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-38725
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/usb/asix_devices.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/75947d3200de98a9ded9ad8972e02f1a177097fe
https://git.kernel.org/stable/c/59ed6fbdb1bc03316e09493ffde7066f031c7524
https://git.kernel.org/stable/c/ccef5ee4adf56472aa26bdd1f821a6d0cd06089a
https://git.kernel.org/stable/c/ee2cd40b0bb46056949a2319084a729d95389386
https://git.kernel.org/stable/c/a754ab53993b1585132e871c5d811167ad3c52ff
https://git.kernel.org/stable/c/ad1f8313aeec0115f9978bd2d002ef4a8d96c773
https://git.kernel.org/stable/c/4faff70959d51078f9ee8372f8cff0d7045e4114
Powered by blists - more mailing lists