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-38149net: phy: clear phydev->devlink when the link is deleted

Description

In the Linux kernel, the following vulnerability has been resolved: net: phy: clear phydev->devlink when the link is deleted There is a potential crash issue when disabling and re-enabling the network port. When disabling the network port, phy_detach() calls device_link_del() to remove the device link, but it does not clear phydev->devlink, so phydev->devlink is not a NULL pointer. Then the network port is re-enabled, but if phy_attach_direct() fails before calling device_link_add(), the code jumps to the "error" label and calls phy_detach(). Since phydev->devlink retains the old value from the previous attach/detach cycle, device_link_del() uses the old value, which accesses a NULL pointer and causes a crash. The simplified crash log is as follows. [ 24.702421] Call trace: [ 24.704856] device_link_put_kref+0x20/0x120 [ 24.709124] device_link_del+0x30/0x48 [ 24.712864] phy_detach+0x24/0x168 [ 24.716261] phy_attach_direct+0x168/0x3a4 [ 24.720352] phylink_fwnode_phy_connect+0xc8/0x14c [ 24.725140] phylink_of_phy_connect+0x1c/0x34 Therefore, phydev->devlink needs to be cleared when the device link is deleted.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 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-38149, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.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.18% · top 92% of all CVEs (15 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 bc66fa87d4fda9053a8145e5718fc278c2b88253 – < 363fdf2777423ad346d781f09548cca14877f729
    • affected bc66fa87d4fda9053a8145e5718fc278c2b88253 – < ddc654e89ace723b78c34911c65243accbc9b75c
    • affected bc66fa87d4fda9053a8145e5718fc278c2b88253 – < 034bc4a2a72dea2cfcaf24c6bae03c38ad5a0b87
    • affected bc66fa87d4fda9053a8145e5718fc278c2b88253 – < 0795b05a59b1371b18ffbf09d385296b12e9f5d5
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References4

Sources

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

Badge for a README or a ticket

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

Record last updated .