CVE-2026-98594: tg3: clean up PHYLIB resources on probe failure
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 0844402326d4e48a28688f93ec6442e93bb442fa, 6515c41503eef849abd2c7364f34e4bb25110f90, a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 0844402326d4e48a28688f93ec6442e93bb442fa, 6515c41503eef849abd2c7364f34e4bb25110f90, a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 6.6.159.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.2% · 12th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 2.6.27affected
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before ce86d6929d03e6b0abcb781dfa50f9f0816bff78affected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81dfaffected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before 0844402326d4e48a28688f93ec6442e93bb442faaffected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before e766321288b507afb70d2bfef6ba443213329f79affected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before d2abb0013b933d59ee441185df0eca9e8c0b33ebaffected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before 6515c41503eef849abd2c7364f34e4bb25110f90affected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3daffected · git
- 158d7abdae85e9ac43d99780c372d79c119f7626 and later · before a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6adaffected · git
- before 2.6.27not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.113-1~deb12u1 | 6.12.113-1~deb12u1 |
| Debian:13 | linux | before 6.12.113-1 | 6.12.113-1 |
| Debian:14 | linux | before 7.2.9-1 | 7.2.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-98592Oct 18, 2026 · net: spacemit: clear TX descriptor on fragment mapping failure0Monitor
- ← EarlierCVE-2026-98593Oct 18, 2026 · s390/debug: Fix NULL pointer dereference in debug_info_copy()0Monitor
- Later →CVE-2026-98595Oct 18, 2026 · udp: remove a disconnected socket from the 4-tuple hash table0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0844402326d4e48a28688f93ec6442e93bb442fa | Vendor (CNA) |
| Linux Linux | 6515c41503eef849abd2c7364f34e4bb25110f90 | Vendor (CNA) |
| Linux Linux | a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df | Vendor (CNA) |
| Linux Linux | a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6ad | Vendor (CNA) |
| Linux Linux | b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3d | Vendor (CNA) |
| Linux Linux | ce86d6929d03e6b0abcb781dfa50f9f0816bff78 | Vendor (CNA) |
| Linux Linux | d2abb0013b933d59ee441185df0eca9e8c0b33eb | Vendor (CNA) |
| Linux Linux | e766321288b507afb70d2bfef6ba443213329f79 | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | 6.6.159.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.113-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 10, 2026+23 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-1351 · Oct 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/6515c41503eef849abd2c7364f34e4bb25110f90
- git.kernel.org/stable/c/a449eedb3b1eb5b8b1f5ed116a1bfe85eaaf81df
- git.kernel.org/stable/c/a92e1a412c53dc0d9ad639e7abf8b3fc70a5b6ad
- git.kernel.org/stable/c/b6c0c757c65893ad7bb17e8bcf33cdd8257d7b3d
- git.kernel.org/stable/c/ce86d6929d03e6b0abcb781dfa50f9f0816bff78
- git.kernel.org/stable/c/d2abb0013b933d59ee441185df0eca9e8c0b33eb
- git.kernel.org/stable/c/e766321288b507afb70d2bfef6ba443213329f79
Vendor advisories and official records. Exploit/PoC links are deliberately left out.