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-2026-98594tg3: clean up PHYLIB resources on probe failure

Description

In the Linux kernel, the following vulnerability has been resolved: tg3: clean up PHYLIB resources on probe failure tg3_get_invariants() can register an MDIO bus and connect a PHY for USE_PHYLIB devices. If tg3_init_one() later fails, its common error path releases the mappings and netdev without undoing those PHYLIB resources. Disconnect the PHY and unregister the MDIO bus before the remaining teardown. Guard PHY cleanup with USE_PHYLIB to match tg3_phy_init(), and call tg3_mdio_fini() unconditionally to match tg3_mdio_init(). The existing IS_CONNECTED and MDIOBUS_INITED flags make both helpers safe when initialization only completed partially. This issue was identified during our ongoing static-analysis research while reviewing kernel code.

Timeline

  1. ID reserved

    By Linux

  2. · 23 days later

    Published

  3. · 1 day 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

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 88% 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: Not scored.

Affected products

  • Linux · Linux

    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < ce86d6929d03e6b0abcb781dfa50f9f0816bff78
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < 0844402326d4e48a28688f93ec6442e93bb442fa
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < e766321288b507afb70d2bfef6ba443213329f79
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < d2abb0013b933d59ee441185df0eca9e8c0b33eb
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < 6515c41503eef849abd2c7364f34e4bb25110f90
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3d
    • affected 158d7abdae85e9ac43d99780c372d79c119f7626 – < a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6ad
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 5.10.271 – ≤ 5.10.*
    • unaffected 5.15.222 – ≤ 5.15.*
    • unaffected 6.1.189 – ≤ 6.1.*
    • unaffected 6.6.158 – ≤ 6.6.*
    • unaffected 6.12.112 – ≤ 6.12.*
    • unaffected 6.18.55 – ≤ 6.18.*
    • unaffected 7.2.9 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

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

Badge for a README or a ticket

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

Record last updated .