CVE-2026-53232

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. the CNA's CVSS baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:linux, epss, ghsa
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

net: phy: clean the sfp upstream if phy probing fails

Sashiko reported that we don't call sfp_bus_del_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be used later on during SFP events.

This issue existed before the generic phylib sfp support, back when drivers were calling phy_sfp_probe themselves.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

June 25, 2026

Last Modified

August 5, 2026

Advisory Details (1)

Auto-updated Jun 28, 2026
No patch confirmed yet.
generic

net: phy: clean the sfp upstream if phy probing fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/48774e87bbaa0056819d4b52301e4692e50e3252

Vendor Advisories for CVE-2026-53232(2)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (350 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (145 versions)7.0.13-1

Data Freshness Timeline

(refreshed 5× in last 7d / 62× 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 218 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-53232?
CVE-2026-53232 is a high vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: phy: clean the sfp upstream if phy probing fails Sashiko reported that we don't call sfpbusdel_upstream() in the probe failure path, so let's add it, otherwise the sfp-bus is left with a dangling 'upstream' field, that may be…
When was CVE-2026-53232 disclosed?
CVE-2026-53232 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53232 actively exploited?
CVE-2026-53232 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 66.7% of all scored CVEs.
What is the CVSS score of CVE-2026-53232?
CVE-2026-53232 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-53232?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53232, 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-53232

Explore →

Is Your Infrastructure Affected by CVE-2026-53232?

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