CVE-2025-37945

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 5.5 from GitHub Security Advisory published 2025-05-20. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-15839 (ENISA EUVD) · GHSA-x689-8m9r-8332 (GitHub Security Advisories)Source: ENISA EUVD

5.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%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: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY

DSA has 2 kinds of drivers:

  • Those who call dsa_switch_suspend() and dsa_switch_resume() from
their device PM ops: qca8k-8xxx, bcm_sf2, microchip ksz
  • Those who don't: all others. The above methods should be optional.

For type 1, dsa_switch_suspend() calls dsa_user_suspend() -> phylink_stop(), and dsa_switch_resume() calls dsa_user_resume() -> phylink_start(). These seem good candidates for setting mac_managed_pm = true because that is essentially its definition [1], but that does not seem to be the biggest problem for now, and is not what this change focuses on.

Talking strictly about the 2nd category of DSA drivers here (which do not have MAC managed PM, meaning that for their attached PHYs, mdio_bus_phy_suspend() and mdio_bus_phy_resume() should run in full), I have noticed that the following warning from mdio_bus_phy_resume() is triggered:

WARN_ON(phydev->state != PHY_HALTED && phydev->state != PHY_READY && phydev->state != PHY_UP);

because the PHY state machine is running.

It's running as a result of a previous dsa_user_open() -> ... -> phylink_start() -> phy_start() having been initiated by the user.

The previous mdio_bus_phy_suspend() was supposed to have called phy_stop_machine(), but it didn't. So this is why the PHY is in state PHY_NOLINK by the time mdio_bus_phy_resume() runs.

mdio_bus_phy_suspend() did not call phy_stop_machine() because for phylink, the phydev->adjust_link function pointer is NULL. This seems a technicality introduced by commit fddd91016d16 ("phylib: fix PAL state machine restart on resume"). That commit was written before phylink existed, and was intended to avoid crashing with consumer drivers which don't use the PHY state machine - phylink always does, when using a PHY. But phylink itself has historically not been developed with suspend/resume in mind, and apparently not tested too much in that scenario, allowing this bug to exist unnoticed for so long. Plus, prior to the WARN_ON(), it would have likely been invisible.

This issue is not in fact restricted to type 2 DSA drivers (according to the above ad-hoc classification), but can be extrapolated to any MAC driver with phylink and MDIO-bus-managed PHY PM ops. DSA is just where the issue was reported. Assuming mac_managed_pm is set correctly, a quick search indicates the following other drivers might be affected:

$ grep -Zlr PHYLINK_NETDEV drivers/ | xargs -0 grep -L mac_managed_pm drivers/net/ethernet/atheros/ag71xx.c drivers/net/ethernet/microchip/sparx5/sparx5_main.c drivers/net/ethernet/microchip/lan966x/lan966x_main.c drivers/net/ethernet/freescale/dpaa2/dpaa2-mac.c drivers/net/ethernet/freescale/fs_enet/fs_enet-main.c drivers/net/ethernet/freescale/dpaa/dpaa_eth.c drivers/net/ethernet/freescale/ucc_geth.c drivers/net/ethernet/freescale/enetc/enetc_pf_common.c drivers/net/ethernet/marvell/mvpp2/mvpp2_main.c drivers/net/ethernet/marvell/mvneta.c drivers/net/ethernet/marvell/prestera/prestera_main.c drivers/net/ethernet/mediatek/mtk_eth_soc.c drivers/net/ethernet/altera/altera_tse_main.c drivers/net/ethernet/wangxun/txgbe/txgbe_phy.c drivers/net/ethernet/meta/fbnic/fbnic_phylink.c drivers/net/ethernet/tehuti/tn40_phy.c drivers/net/ethernet/mscc/ocelot_net.c

Make the existing conditions dependent on the PHY device having a phydev->phy_link_change() implementation equal to the default phy_link_change() provided by phylib. Otherwise, we implicitly know that the phydev has the phylink-provided phylink_phy_change() callback, and when phylink is used, the PHY state machine always needs to be stopped/ started on the suspend/resume path. The code is structured as such that if phydev->phy_link_change() is absent, it is a matter of time until the kernel will crash - no need to further complicate the test.

Thus, for the situation where the PM is not managed b ---truncated---

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

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
11th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity
5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 20, 2025

Last Modified

October 15, 2026

Advisory Details (8)

Auto-updated Jul 17, 2026
Patch available.
Web page

SSA-082556

https://cert-portal.siemens.com/productcert/html/ssa-082556.html
Web page

SSA-019113

https://cert-portal.siemens.com/productcert/html/ssa-019113.html
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fc75ea20ffb452652f0d4033f38fe88d7cfdae35
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bd4037d51d3f6667636a1383e78e48a5b7b60755
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a6ed6f8ec81b8ca7100dcd9e62bdbc0dff1b2259
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54e5d00a8de6c13f6c01a94ed48025e882cd15f7
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/17eef1e44883845b9567afc893dc41e004c08d65
Web page

net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/043aa41c43f8cb9cce75367ea07895ce68b5abb0

Vendor Advisories for CVE-2025-37945(2)

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

Patch Availability(20)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1041.42) @ noble2026-09-08ubuntu
ubuntulinux-tools-realtime-hwe-22.04 (6.8.1-1041.42~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-09-08ubuntu
ubuntulinux-tools-fips-6.8 (6.8.0-100.100+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1046.49.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1044.44) @ noble2026-09-08ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1023.24) @ noble2026-09-08ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-gke-64k-6.8 (6.8.0-1043.48) @ noble2026-09-08ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (6.8.0-100.100.1) @ noble2026-09-08ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1047.50+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure (6.14.0-1007.7) @ plucky2026-09-08ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-22.22) @ plucky2026-09-08ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-09-08ubuntu
ubuntulinux-tools-oracle-64k (6.14.0-1007.7) @ plucky2026-09-08ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-09-08ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-09-08ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1046.52) @ noble2026-09-08ubuntu
linuxKernel @ 6.1.168 (fixes >=6.0.0)—osv

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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.164-1~deb11u1 (16 versions)
  • every version up to 6.1.170-1~deb11u1: fixed in 6.1.170-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (48 versions)
  • every version up to 6.1.170-1: fixed in 6.1.170-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.12.25-1: fixed in 6.12.25-1
—

Weakness Classification(1)

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

All Vendor Advisories

(19)

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 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 225 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-37945?
CVE-2025-37945 is a medium-severity vulnerability; its CVE record was published on May 20, 2025. In the Linux kernel, the following vulnerability has been resolved: net: phy: allow MDIO bus PM ops to start/stop state machine for phylink-controlled PHY DSA has 2 kinds of drivers: 1. Those who call dsa_switch_suspend() and dsa_switch_resume() from their device PM ops: qca8k-8xxx, bcm_sf2,…
When was the CVE record for CVE-2025-37945 published?
The CVE record for CVE-2025-37945 was published on May 20, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 15, 2026; the record at its source may have been updated since.
Is CVE-2025-37945 actively exploited?
CVE-2025-37945 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-37945?
CVE-2025-37945 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2025-37945?
A fix for CVE-2025-37945 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-37945 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-2025-37945

Explore →

Is Your Infrastructure Affected by CVE-2025-37945?

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

Book a Demo →Browse All CVEs