CVE-2025-59610

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

Score 6.4 from GitHub Security Advisory published 2026-06-02. a secondary CVSS source baseline 6.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.4Exploit: NoneExposed: 0

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

Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.

CVSS v3
6.4
EG Score
6.4(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
Severity64% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
0.0%
KEV
Not listed

Published

June 1, 2026

Last Modified

July 22, 2026

Advisory Details (1)

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

Qualcomm Documentation

https://docs.qualcomm.com/product/publicresources/securitybulletin/june-2026-bulletin.html

Vendor Advisories for CVE-2025-59610(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 1× in last 7d / 18× 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-07-23 03:00 UTCEG score recompute
  2. 2026-07-16 01:17 UTCGHSA enrichment
  3. 2026-07-14 03:48 UTCGHSA enrichment
  4. 2026-07-11 13:16 UTCGHSA enrichment
  5. 2026-07-08 16:46 UTCGHSA enrichment
  6. 2026-07-08 15:15 UTCEPSS rescore
  7. 2026-07-07 13:45 UTCEPSS rescore
  8. 2026-07-04 00:18 UTCGHSA enrichment
  9. 2026-07-02 23:46 UTCGHSA enrichment
  10. 2026-07-02 00:05 UTCGHSA enrichment
  11. 2026-07-01 00:21 UTCGHSA enrichment
  12. 2026-06-30 00:25 UTCGHSA enrichment
  13. 2026-06-29 00:44 UTCGHSA enrichment
  14. 2026-06-28 01:05 UTCGHSA enrichment
  15. 2026-06-27 01:20 UTCGHSA enrichment
  16. 2026-06-26 01:30 UTCGHSA enrichment
  17. 2026-06-25 01:06 UTCGHSA enrichment
  18. 2026-06-24 01:27 UTCGHSA enrichment
  19. 2026-06-20 13:27 UTCGHSA enrichment
  20. 2026-06-18 21:44 UTCGHSA enrichment
  21. 2026-06-17 18:29 UTCGHSA enrichment
  22. 2026-06-16 18:50 UTCGHSA enrichment
  23. 2026-06-15 19:10 UTCGHSA enrichment
  24. 2026-06-15 17:48 UTCEPSS rescore
  25. 2026-06-14 23:17 UTCEPSS rescore
Show 34 more
  1. 2026-06-14 18:25 UTCGHSA enrichment
  2. 2026-06-13 23:00 UTCEPSS rescore
  3. 2026-06-13 18:46 UTCGHSA enrichment
  4. 2026-06-12 23:11 UTCEPSS rescore
  5. 2026-06-12 18:35 UTCGHSA enrichment
  6. 2026-06-11 18:56 UTCGHSA enrichment
  7. 2026-06-11 14:00 UTCEPSS rescore
  8. 2026-06-11 14:00 UTCEPSS rescore
  9. 2026-06-10 22:18 UTCEPSS rescore
  10. 2026-06-10 22:18 UTCEPSS rescore
  11. 2026-06-10 19:18 UTCGHSA enrichment
  12. 2026-06-10 13:22 UTCEPSS rescore
  13. 2026-06-10 13:22 UTCEPSS rescore
  14. 2026-06-09 19:39 UTCGHSA enrichment
  15. 2026-06-08 20:01 UTCGHSA enrichment
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-07 20:23 UTCGHSA enrichment
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-07 15:24 UTCEPSS rescore
  21. 2026-06-06 20:45 UTCGHSA enrichment
  22. 2026-06-05 22:46 UTCEPSS rescore
  23. 2026-06-05 22:46 UTCEPSS rescore
  24. 2026-06-05 21:07 UTCGHSA enrichment
  25. 2026-06-05 06:10 UTCEPSS rescore
  26. 2026-06-05 06:10 UTCEPSS rescore
  27. 2026-06-04 21:29 UTCGHSA enrichment
  28. 2026-06-04 13:12 UTCEPSS rescore
  29. 2026-06-04 13:12 UTCEPSS rescore
  30. 2026-06-03 21:50 UTCGHSA enrichment
  31. 2026-06-02 22:11 UTCGHSA enrichment
  32. 2026-06-02 20:12 UTCEPSS rescore
  33. 2026-06-02 20:12 UTCEPSS rescore
  34. 2026-06-01 22:32 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-59610?
CVE-2025-59610 is a medium vulnerability published on June 1, 2026. Memory Corruption when processing IOCTL requests with mismatched API versions due to concurrent modification of user-space buffer.
When was CVE-2025-59610 disclosed?
CVE-2025-59610 was first published in the National Vulnerability Database on June 1, 2026, with the most recent update on July 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-59610 actively exploited?
CVE-2025-59610 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-59610?
CVE-2025-59610 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2025-59610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-59610, 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

Explore the affected products and dependency analysis for CVE-2025-59610

Explore →

Is Your Infrastructure Affected by CVE-2025-59610?

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

Start Free Scan →Browse All CVEs