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-39805net: macb: fix unregister_netdev call order in macb_remove()

Description

In the Linux kernel, the following vulnerability has been resolved: net: macb: fix unregister_netdev call order in macb_remove() When removing a macb device, the driver calls phy_exit() before unregister_netdev(). This leads to a WARN from kernfs: ------------[ cut here ]------------ kernfs: can not remove 'attached_dev', no directory WARNING: CPU: 1 PID: 27146 at fs/kernfs/dir.c:1683 Call trace: kernfs_remove_by_name_ns+0xd8/0xf0 sysfs_remove_link+0x24/0x58 phy_detach+0x5c/0x168 phy_disconnect+0x4c/0x70 phylink_disconnect_phy+0x6c/0xc0 [phylink] macb_close+0x6c/0x170 [macb] ... macb_remove+0x60/0x168 [macb] platform_remove+0x5c/0x80 ... The warning happens because the PHY is being exited while the netdev is still registered. The correct order is to unregister the netdev before shutting down the PHY and cleaning up the MDIO bus. Fix this by moving unregister_netdev() ahead of phy_exit() in macb_remove().

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 8 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-39805, 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.17% · top 94% of all CVEs (18 Nov 2026)
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 8b73fa3ae02b2401960de41b0454c0321377b203 – < 7351782f2fc8ac31ced52e3d4e6fa120f819a7ab
    • affected 8b73fa3ae02b2401960de41b0454c0321377b203 – < 2b9719ccad38dffad7dbdd2f39896f723f9b9011
    • affected 8b73fa3ae02b2401960de41b0454c0321377b203 – < ff0d3bad32108b57265e5b48f15327549af771d3
    • affected 8b73fa3ae02b2401960de41b0454c0321377b203 – < 775fe690fd4a3337ad2115de2adb41b227d4dae7
    • affected 8b73fa3ae02b2401960de41b0454c0321377b203 – < 01b9128c5db1b470575d07b05b67ffa3cb02ebf1
  • Linux · Linux

    • affected 5.18
    • unaffected < 5.18
    • unaffected 6.1.159 – ≤ 6.1.*
    • unaffected 6.6.119 – ≤ 6.6.*
    • unaffected 6.12.45 – ≤ 6.12.*
    • unaffected 6.16.5 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .