CVE-2026-64107

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

ASoC: codecs: pcm512x: fix null-ptr dereference in pcm512x_overclock_xxx_put()

In the pcm512x chipset driver, pcm512x_overclock_xxx_put() is defined as a general mixer kcontrol instead of a DAPM kcontrol, so struct snd_soc_dapm_context must not be accessed via snd_soc_dapm_kcontrol_to_dapm().

This causes a NULL pointer dereference, so it must be modified to use snd_soc_component_to_dapm().

CVSS v3
5.5
EG Score
5.5(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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 12, 2026

Advisory Details (2)

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

ASoC: codecs: pcm512x: fix null-ptr dereference in pcm512x_overclock_xxx_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/285159ca199cbbe424223d4b14db227b279b5767
generic

ASoC: codecs: pcm512x: fix null-ptr dereference in pcm512x_overclock_xxx_put() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09e8f9a9aa19aa8c1b0cc7a0ebc68f6ecf86a660

Vendor Advisories for CVE-2026-64107(1)

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

Patch Availability(5)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ 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

(5)

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 18× in last 7d / 78× 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 108 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-64107?
CVE-2026-64107 is a medium vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: pcm512x: fix null-ptr dereference in pcm512xoverclockxxx_put() In the pcm512x chipset driver, pcm512xoverclockxxx_put() is defined as a general mixer kcontrol instead of a DAPM kcontrol, so struct sndsocdapm_context…
When was CVE-2026-64107 disclosed?
CVE-2026-64107 was first published in the National Vulnerability Database on July 19, 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-64107 actively exploited?
CVE-2026-64107 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.5% of all scored CVEs.
What is the CVSS score of CVE-2026-64107?
CVE-2026-64107 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-64107?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64107, 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-64107

Explore →

Is Your Infrastructure Affected by CVE-2026-64107?

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

Start Free Scan →Browse All CVEs