CVE-2026-64243

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
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:

ASoC: codecs: simple-mux: Fix enum control bounds check

simple_mux_control_put() rejects values greater than e->items, but enum control values are zero based. For the two-entry mux used by this driver, valid values are 0 and 1, so value 2 must be rejected as well.

Accepting e->items can store an invalid mux state, pass it to the GPIO setter, and pass it on to the DAPM mux update path where it is used as an index into the enum text array.

Use the same >= e->items check used by the ASoC enum helpers.

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 17, 2026

Advisory Details (7)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6fb653b62f169f6050fac45b56bf21ad097e19f6
generic

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5fe860af8630cf7c78523cbd68e5a234743585aa
generic

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2ff3ac6f7664fe5639cad01712ac5e021fa7939c
generic

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/164dcbec9632ca93ae313e6da6e4e05584fa0f02
generic

ASoC: codecs: simple-mux: Fix enum control bounds check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/05ef77f02607a3dc5d7f9762cb990f76843315d4

Vendor Advisories for CVE-2026-64243(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-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-27ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-27ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-27ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1—
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 (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 43× in last 7d / 179× 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 198 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-64243?
CVE-2026-64243 is a high vulnerability published on July 24, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: simple-mux: Fix enum control bounds check simplemuxcontrol_put() rejects values greater than e->items, but enum control values are zero based. For the two-entry mux used by this driver, valid values are 0 and 1, so…
When was CVE-2026-64243 disclosed?
CVE-2026-64243 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64243 actively exploited?
CVE-2026-64243 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-64243?
CVE-2026-64243 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-64243?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64243, 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-64243

Explore →

Is Your Infrastructure Affected by CVE-2026-64243?

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

Start Free Scan →Browse All CVEs