Skip to main content
VulnerabilityPublished Updated

CVE-2025-38725: Linux kernel · net: usb: asix_devices: add phy_mask for ax88772 mdio bus

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in ee2cd40b0bb46056949a2319084a729d95389386 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in ee2cd40b0bb46056949a2319084a729d95389386, ccef5ee4adf56472aa26bdd1f821a6d0cd06089a, ad1f8313aeec0115f9978bd2d002ef4a8d96c773 +4

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < ee2cd40b0bb46056949a2319084a729d95389386
Fixed in
  • ee2cd40b0bb46056949a2319084a729d95389386
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < ccef5ee4adf56472aa26bdd1f821a6d0cd06089a
Fixed in
  • ccef5ee4adf56472aa26bdd1f821a6d0cd06089a
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < ad1f8313aeec0115f9978bd2d002ef4a8d96c773
Fixed in
  • ad1f8313aeec0115f9978bd2d002ef4a8d96c773
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < a754ab53993b1585132e871c5d811167ad3c52ff
Fixed in
  • a754ab53993b1585132e871c5d811167ad3c52ff
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < 75947d3200de98a9ded9ad8972e02f1a177097fe
Fixed in
  • 75947d3200de98a9ded9ad8972e02f1a177097fe
LinuxLinuxAffected
  • ≥ e532a096be0e5e570b383e71d4560e7f04384e0f, < 59ed6fbdb1bc03316e09493ffde7066f031c7524
Fixed in
  • 59ed6fbdb1bc03316e09493ffde7066f031c7524

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.

References

Community reviews

Loading reviews…