CVE-2026-64209

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-24. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

phy: qcom: qmp-usbc: Fix out-of-bounds array access in dp swing config

swing_tbl and pre_emphasis_tbl are 4x4 arrays (valid indices 0-3), but the boundary check uses "> 4" instead of ">= 4", allowing index 4 to cause an out-of-bounds access.

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

Published

July 24, 2026

Last Modified

August 12, 2026

Advisory Details (2)

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

phy: qcom: qmp-usbc: Fix out-of-bounds array access in dp swing config - kernel/git/stable/linux.git - Linux kernel stable tree

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

phy: qcom: qmp-usbc: Fix out-of-bounds array access in dp swing config - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/cb35af6e7f3d5628178b58c631e305b1def8edf7

Vendor Advisories for CVE-2026-64209(1)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu

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

(3)

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 32× in last 7d / 115× 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 133 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64209?
CVE-2026-64209 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: phy: qcom: qmp-usbc: Fix out-of-bounds array access in dp swing config swingtbl and preemphasis_tbl are 4x4 arrays (valid indices 0-3), but the boundary check uses "> 4" instead of ">= 4", allowing index 4 to cause an out-of-bounds…
When was CVE-2026-64209 disclosed?
CVE-2026-64209 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64209 actively exploited?
CVE-2026-64209 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 98.1% of all scored CVEs.
What is the CVSS score of CVE-2026-64209?
CVE-2026-64209 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64209?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64209, 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-64209

Explore →

Is Your Infrastructure Affected by CVE-2026-64209?

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

Start Free Scan →Browse All CVEs