CVE-2026-64120

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-07-19. 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: fix NULL pointer dereference in phy_reply_size

In phy_prepare_data(), several strings such as 'name', 'drvname', 'upstream_sfp_name', and 'downstream_sfp_name' are allocated using kstrdup(). However, these allocations were not checked for failure.

If kstrdup() fails for 'name', it returns NULL while the function continues. This leads to a kernel NULL pointer dereference and panic later in phy_reply_size() when it unconditionally calls strlen() on the NULL pointer.

While other strings like 'upstream_sfp_name' might be checked before access in certain code paths, failing to handle these allocations consistently can lead to incomplete data reporting or hidden bugs.

Fix this by adding proper NULL checks for all kstrdup() calls in phy_prepare_data() and implement a centralized error handling path using goto labels to ensure all previously allocated resources are freed on failure.

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 19, 2026

Last Modified

August 13, 2026

Advisory Details (3)

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

net: ethtool: fix NULL pointer dereference in phy_reply_size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61f53c1e58d68723bc1db10912a53f1991f08719
generic

net: ethtool: fix NULL pointer dereference in phy_reply_size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4908f1395fb1b832ceec11584af649874a2732ea
generic

net: ethtool: fix NULL pointer dereference in phy_reply_size - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3dbe20a3809347bacda890822e7ca013bd85a18c

Vendor Advisories for CVE-2026-64120(1)

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

Patch Availability(5)

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

(5)

Data Freshness Timeline

(refreshed 22× in last 7d / 83× 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.

Showing the most recent 100 of 113 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64120?
CVE-2026-64120 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: net: ethtool: fix NULL pointer dereference in phyreplysize In phypreparedata(), several strings such as 'name', 'drvname', 'upstreamsfpname', and 'downstreamsfpname' are allocated using kstrdup(). However, these allocations were…
When was CVE-2026-64120 disclosed?
CVE-2026-64120 was first published in the National Vulnerability Database on July 19, 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-64120 actively exploited?
CVE-2026-64120 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-64120?
CVE-2026-64120 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64120?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64120, 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-64120

Explore →

Is Your Infrastructure Affected by CVE-2026-64120?

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