CVE-2026-53231

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: <0.1%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

net: phy: don't try to setup PHY-driven SFP cages when using genphy

We don't have support for PHY-driver SFP cages with the genphy code.

On top of that, it was found by sashiko that running sfp_bus_add_upstream() for genphy deadlocks, as for genphy the PHY probing runs under RTNL, which isn't the case for non-genphy drivers.

This problem was reproduced, and does lead to a deadlock on RTNL.

Before the blamed commit, the phy_sfp_probe() call was made by individual PHY drivers, so there was no way to get to the SFP probing path when using genphy.

Let's therefore only run phy_sfp_probe when not using genphy.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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%
EPSS PROB
<0.1%
EPSS %ILE
below the 1st
KEV
Not listed

Published

June 25, 2026

Last Modified

July 2, 2026

Advisory Details (2)

Auto-updated Jul 3, 2026
Patch available.
generic

net: phy: don't try to setup PHY-driven SFP cages when using genphy - kernel/git/stable/linux.git - Linux kernel stable tree

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

net: phy: don't try to setup PHY-driven SFP cages when using genphy - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a0082ec20a05ef2378410323a5089a8f1786f4a

Vendor Advisories for CVE-2026-53231(1)

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

Patch Availability(10)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-23ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-23ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-09-23ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-09-23ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-09-23ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-09-23ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-09-23ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-09-23ubuntu

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 rangeFix by version rangeDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)
  • every version up to 7.0.13-1: fixed in 7.0.13-1
—

Weakness Classification(1)

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

All Vendor Advisories

(10)

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 5× in last 7d / 30× 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 163 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-53231?
CVE-2026-53231 is a medium vulnerability published on June 25, 2026. In the Linux kernel, the following vulnerability has been resolved: net: phy: don't try to setup PHY-driven SFP cages when using genphy We don't have support for PHY-driver SFP cages with the genphy code. On top of that, it was found by sashiko that running sfpbusadd_upstream() for genphy…
When was CVE-2026-53231 disclosed?
CVE-2026-53231 was first published on June 25, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53231 actively exploited?
CVE-2026-53231 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a <0.1% probability of exploitation in the next 30 days (below the 1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-53231?
CVE-2026-53231 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53231?
A fix for CVE-2026-53231 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-53231 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-53231?

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

Book a Demo →Browse All CVEs