Live › vulnerability › CVE-2026-98594
Go to dashboardThe tg3 Ethernet driver in the Linux kernel does not release its PHYLIB MDIO bus and connected PHY when device probing fails partway. The sources describe a resource cleanup gap; they do not describe an attacker-triggered exploit.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
Systems that load the tg3 driver for Broadcom NICs with PHYLIB support, where the driver initialization can fail after registering an MDIO bus. Systems without Broadcom tg3 hardware, or that do not use the tg3 module, are not affected.
No product ranges from the sources yet.
uname -r and compare against the kernel version that carries the upstream tg3 fix, which the sources do not namelsmod | grep tg3 and whether the NIC uses it (lspci -k | grep -A3 -i ethernet)Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-98594")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.