CVE-2026-63838

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

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

ASoC: rsnd: Fix potential out-of-bounds access of component_dais[]

component_dais[RSND_MAX_COMPONENT] is initially zero-initialized and later populated in rsnd_dai_of_node(). However, the existing boundary check: if (i >= RSND_MAX_COMPONENT)

does not guarantee that the last valid element remains zero. As a result, the loop can rely on component_dais[RSND_MAX_COMPONENT] being zero, which may lead to an out-of-bounds access.

Found by Linux Verification Center (linuxtesting.org) with SVACE.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
8%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 27, 2026

Vendor Advisories for CVE-2026-63838(1)

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

Patch Availability(18)

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

(2 across 2 ecosystems)
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 (137 versions)7.0.10-1

All Vendor Advisories

(18)

Data Freshness Timeline

(refreshed 11× in last 7d / 47× 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-08-30 06:58 UTCVendor advisory
  2. 2026-08-30 06:58 UTCGHSA enrichment
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 11:58 UTCVendor advisory
  7. 2026-08-27 11:58 UTCGHSA enrichment
  8. 2026-08-26 14:46 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 15:59 UTCVendor advisory
  11. 2026-08-24 15:59 UTCGHSA enrichment
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 20:55 UTCVendor advisory
  15. 2026-08-21 20:55 UTCGHSA enrichment
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 17:04 UTCEPSS rescore
  18. 2026-08-19 01:54 UTCVendor advisory
  19. 2026-08-19 01:54 UTCGHSA enrichment
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 13:47 UTCEPSS rescore
  22. 2026-08-16 14:56 UTCEPSS rescore
  23. 2026-08-16 06:54 UTCVendor advisory
  24. 2026-08-16 06:54 UTCGHSA enrichment
  25. 2026-08-15 01:30 UTCEPSS rescore
Show 53 more
  1. 2026-08-13 11:54 UTCVendor advisory
  2. 2026-08-13 11:54 UTCGHSA enrichment
  3. 2026-08-12 13:51 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 16:54 UTCVendor advisory
  6. 2026-08-10 16:54 UTCGHSA enrichment
  7. 2026-08-09 13:47 UTCEPSS rescore
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-07 21:54 UTCVendor advisory
  10. 2026-08-07 21:54 UTCGHSA enrichment
  11. 2026-08-06 13:47 UTCEPSS rescore
  12. 2026-08-05 19:17 UTCEPSS rescore
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-05 02:54 UTCVendor advisory
  15. 2026-08-05 02:54 UTCGHSA enrichment
  16. 2026-08-04 15:10 UTCEPSS rescore
  17. 2026-08-04 10:39 UTCEPSS rescore
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 07:55 UTCVendor advisory
  20. 2026-08-02 07:55 UTCGHSA enrichment
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 12:55 UTCEG score recompute
  25. 2026-07-30 12:55 UTCVendor advisory
  26. 2026-07-30 12:54 UTCGHSA enrichment
  27. 2026-07-30 01:30 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-28 15:37 UTCEPSS rescore
  30. 2026-07-27 17:53 UTCGHSA enrichment
  31. 2026-07-27 14:14 UTCEPSS rescore
  32. 2026-07-26 14:54 UTCEPSS rescore
  33. 2026-07-26 14:54 UTCEPSS rescore
  34. 2026-07-26 11:07 UTCEG score recompute
  35. 2026-07-26 11:07 UTCVendor advisory
  36. 2026-07-26 11:07 UTCGHSA enrichment
  37. 2026-07-25 14:18 UTCEPSS rescore
  38. 2026-07-25 14:18 UTCEPSS rescore
  39. 2026-07-24 14:18 UTCEPSS rescore
  40. 2026-07-24 14:18 UTCEPSS rescore
  41. 2026-07-23 14:18 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 03:22 UTCEG score recompute
  44. 2026-07-22 14:08 UTCEPSS rescore
  45. 2026-07-22 14:08 UTCEPSS rescore
  46. 2026-07-21 15:25 UTCEPSS rescore
  47. 2026-07-21 15:25 UTCEPSS rescore
  48. 2026-07-20 17:42 UTCEG score recompute
  49. 2026-07-20 17:42 UTCGHSA enrichment
  50. 2026-07-20 17:08 UTCEPSS rescore
  51. 2026-07-19 15:51 UTCNVD update
  52. 2026-07-19 14:35 UTCEG score recompute
  53. 2026-07-19 14:34 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-63838?
CVE-2026-63838 is a publicly disclosed vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: rsnd: Fix potential out-of-bounds access of component_dais[] componentdais[RSNDMAX_COMPONENT] is initially zero-initialized and later populated in rsnddaiof_node(). However, the existing boundary check: if (i >=…
When was CVE-2026-63838 disclosed?
CVE-2026-63838 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63838 actively exploited?
CVE-2026-63838 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 91.9% of all scored CVEs.
How do I remediate CVE-2026-63838?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-63838, 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-63838

Explore →

Is Your Infrastructure Affected by CVE-2026-63838?

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