Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 14 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-38725, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < 75947d3200de98a9ded9ad8972e02f1a177097fe
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < 59ed6fbdb1bc03316e09493ffde7066f031c7524
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < ccef5ee4adf56472aa26bdd1f821a6d0cd06089a
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < ee2cd40b0bb46056949a2319084a729d95389386
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < a754ab53993b1585132e871c5d811167ad3c52ff
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < ad1f8313aeec0115f9978bd2d002ef4a8d96c773
    • affected e532a096be0e5e570b383e71d4560e7f04384e0f – < 4faff70959d51078f9ee8372f8cff0d7045e4114
  • Linux · Linux

    • affected 5.14
    • unaffected < 5.14
    • unaffected 5.15.190 – ≤ 5.15.*
    • unaffected 6.1.149 – ≤ 6.1.*
    • unaffected 6.6.103 – ≤ 6.6.*
    • unaffected 6.12.43 – ≤ 6.12.*
    • unaffected 6.15.11 – ≤ 6.15.*
    • unaffected 6.16.2 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-38725 badge
[![CVE-2025-38725](https://cveledger.app/badge/CVE-2025-38725.svg)](https://cveledger.app/cve/CVE-2025-38725)

Record last updated .