CVE-2026-64228

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

net: ethtool: phy: avoid NULL deref when PHY driver is unbound

phydev->drv can become NULL while the phy_device is still attached to its net_device, namely after the PHY driver is unbound via sysfs:

echo > /sys/bus/mdio_bus/drivers//unbind

phy_remove() clears phydev->drv but doesn't call phy_detach(), so the phy_device stays in the link topology xarray and ethnl_req_get_phydev() still hands it back. ETHTOOL_MSG_PHY_GET then oopses on:

rep_data->drvname = kstrdup(phydev->drv->name, GFP_KERNEL);

drvname is already treated as optional by phy_reply_size(), phy_fill_reply() and phy_cleanup_data(), so just skip the allocation when there is no driver bound.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 24, 2026

Last Modified

August 13, 2026

Advisory Details (3)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

net: ethtool: phy: avoid NULL deref when PHY driver is unbound - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e3adf69f8eb121a9128c2b0029efd050d3649153
generic

net: ethtool: phy: avoid NULL deref when PHY driver is unbound - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3586924625559e6f9876d726c80ff0a75f0d5849
generic

net: ethtool: phy: avoid NULL deref when PHY driver is unbound - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17fe2381f967d353183f374a1c0181a6d194158c

Vendor Advisories for CVE-2026-64228(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (138 versions)7.0.12-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(3)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 18× in last 7d / 76× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-30 00:18 UTCEG score recompute
  3. 2026-08-30 00:18 UTCVendor advisory
  4. 2026-08-30 00:18 UTCGHSA enrichment
  5. 2026-08-28 21:42 UTCEPSS rescore
  6. 2026-08-27 13:29 UTCEG score recompute
  7. 2026-08-27 13:29 UTCVendor advisory
  8. 2026-08-27 13:29 UTCGHSA enrichment
  9. 2026-08-26 14:47 UTCEPSS rescore
  10. 2026-08-26 11:36 UTCEG score recompute
  11. 2026-08-26 11:36 UTCGHSA enrichment
  12. 2026-08-25 13:49 UTCEPSS rescore
  13. 2026-08-25 09:42 UTCEG score recompute
  14. 2026-08-25 09:42 UTCVendor advisory
  15. 2026-08-25 09:41 UTCGHSA enrichment
  16. 2026-08-24 07:47 UTCEG score recompute
  17. 2026-08-24 07:47 UTCVendor advisory
  18. 2026-08-24 07:47 UTCGHSA enrichment
  19. 2026-08-23 05:54 UTCEG score recompute
  20. 2026-08-23 05:54 UTCVendor advisory
  21. 2026-08-23 05:54 UTCGHSA enrichment
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-22 04:00 UTCEG score recompute
  24. 2026-08-22 04:00 UTCVendor advisory
  25. 2026-08-22 04:00 UTCGHSA enrichment
Show 69 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-21 02:07 UTCEG score recompute
  3. 2026-08-21 02:07 UTCVendor advisory
  4. 2026-08-21 02:07 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-20 00:12 UTCEG score recompute
  7. 2026-08-20 00:12 UTCVendor advisory
  8. 2026-08-20 00:12 UTCGHSA enrichment
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 22:16 UTCEG score recompute
  11. 2026-08-18 22:16 UTCVendor advisory
  12. 2026-08-18 22:16 UTCGHSA enrichment
  13. 2026-08-18 13:48 UTCEPSS rescore
  14. 2026-08-17 20:22 UTCEG score recompute
  15. 2026-08-17 20:22 UTCVendor advisory
  16. 2026-08-17 20:22 UTCGHSA enrichment
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-16 17:54 UTCEG score recompute
  19. 2026-08-16 17:54 UTCVendor advisory
  20. 2026-08-16 17:54 UTCGHSA enrichment
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-15 16:01 UTCEG score recompute
  23. 2026-08-15 16:01 UTCVendor advisory
  24. 2026-08-15 16:01 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
  26. 2026-08-14 14:07 UTCEG score recompute
  27. 2026-08-14 14:07 UTCVendor advisory
  28. 2026-08-14 14:07 UTCGHSA enrichment
  29. 2026-08-13 22:00 UTCEPSS rescore
  30. 2026-08-13 12:13 UTCEG score recompute▲ 5.50
  31. 2026-08-13 12:13 UTCVendor advisory
  32. 2026-08-13 12:13 UTCGHSA enrichment
  33. 2026-08-13 12:12 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-11 03:49 UTCVendor advisory
  36. 2026-08-11 03:49 UTCGHSA enrichment
  37. 2026-08-11 00:00 UTCEPSS rescore
  38. 2026-08-09 13:47 UTCEPSS rescore
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 06:50 UTCVendor advisory
  41. 2026-08-08 06:50 UTCGHSA enrichment
  42. 2026-08-06 13:47 UTCEPSS rescore
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-05 09:51 UTCGHSA enrichment
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-03 10:36 UTCEPSS rescore
  49. 2026-08-02 12:16 UTCGHSA enrichment
  50. 2026-08-02 02:27 UTCEPSS rescore
  51. 2026-08-01 04:16 UTCEPSS rescore
  52. 2026-07-30 16:28 UTCEPSS rescore
  53. 2026-07-30 15:16 UTCEG score recompute
  54. 2026-07-30 15:16 UTCGHSA enrichment
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-30 01:30 UTCEPSS rescore
  57. 2026-07-29 00:01 UTCEG score recompute
  58. 2026-07-29 00:01 UTCGHSA enrichment
  59. 2026-07-28 15:37 UTCEPSS rescore
  60. 2026-07-27 14:14 UTCEPSS rescore
  61. 2026-07-26 14:54 UTCEPSS rescore
  62. 2026-07-26 14:54 UTCEPSS rescore
  63. 2026-07-26 02:59 UTCEG score recompute
  64. 2026-07-26 02:58 UTCGHSA enrichment
  65. 2026-07-25 14:18 UTCEPSS rescore
  66. 2026-07-25 14:18 UTCEPSS rescore
  67. 2026-07-24 16:31 UTCNVD update
  68. 2026-07-24 15:43 UTCEG score recompute
  69. 2026-07-24 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-64228?
CVE-2026-64228 is a medium vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ethtool: phy: avoid NULL deref when PHY driver is unbound phydev->drv can become NULL while the phy_device is still attached to its net_device, namely after the PHY driver is unbound via sysfs: echo <mdioid> >…
When was CVE-2026-64228 disclosed?
CVE-2026-64228 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64228 actively exploited?
CVE-2026-64228 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.9% of all scored CVEs.
What is the CVSS score of CVE-2026-64228?
CVE-2026-64228 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64228?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64228, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64228

Explore →

Is Your Infrastructure Affected by CVE-2026-64228?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs