CVE-2026-68348

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

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

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

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

ASoC: tas2781: bound firmware description string parsing

The TAS2781 firmware parser reads several variable-length description strings with strlen() before checking that the string terminator is present inside the firmware blob. A malformed firmware image without a NUL terminator can therefore make the parser walk past the end of the firmware buffer before the later size checks run.

Add a small bounded string-length helper and use it for all description fields that are parsed from the firmware buffer. Keep the existing size checks for the fixed bytes that follow each string.

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/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
3%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (5)

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

ASoC: tas2781: bound firmware description string parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: tas2781: bound firmware description string parsing - kernel/git/stable/linux.git - Linux kernel stable tree

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

ASoC: tas2781: bound firmware description string parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/41ae2b7d37c3dd82302167496836cca9f0328374
generic

ASoC: tas2781: bound firmware description string parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ddb0d3e36507615e5ef010a879357a54870adf5
generic

ASoC: tas2781: bound firmware description string parsing - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0ec45e80a82785ee147516fdecf5c93707dec119

Vendor Advisories for CVE-2026-68348(2)

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

Data Freshness Timeline

(refreshed 33× in last 7d / 45× 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-20 22:56 UTCEPSS rescore
  2. 2026-08-20 21:39 UTCGHSA enrichment
  3. 2026-08-20 10:47 UTCGHSA enrichment
  4. 2026-08-19 23:56 UTCEG score recompute
  5. 2026-08-19 23:56 UTCGHSA enrichment
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-19 13:04 UTCGHSA enrichment
  8. 2026-08-19 02:11 UTCGHSA enrichment
  9. 2026-08-18 15:18 UTCEG score recompute
  10. 2026-08-18 15:18 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 04:21 UTCGHSA enrichment
  14. 2026-08-17 17:29 UTCEG score recompute
  15. 2026-08-17 17:29 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:32 UTCEG score recompute
  18. 2026-08-17 06:32 UTCGHSA enrichment
  19. 2026-08-17 05:36 UTCEG score recompute
  20. 2026-08-17 05:36 UTCGHSA enrichment
  21. 2026-08-17 03:47 UTCGHSA enrichment
  22. 2026-08-16 16:55 UTCEG score recompute
  23. 2026-08-16 16:55 UTCGHSA enrichment
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 06:03 UTCEG score recompute
Show 20 more
  1. 2026-08-16 06:03 UTCGHSA enrichment
  2. 2026-08-15 19:12 UTCGHSA enrichment
  3. 2026-08-15 08:20 UTCEG score recompute
  4. 2026-08-15 08:20 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 21:28 UTCGHSA enrichment
  7. 2026-08-14 10:37 UTCEG score recompute
  8. 2026-08-14 10:37 UTCGHSA enrichment
  9. 2026-08-13 23:45 UTCEG score recompute
  10. 2026-08-13 23:45 UTCGHSA enrichment
  11. 2026-08-13 23:04 UTCEG score recompute 7.10
  12. 2026-08-13 23:04 UTCGHSA enrichment
  13. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-13 13:57 UTCEG score recompute
  16. 2026-08-13 13:57 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-10 13:24 UTCNVD update
  19. 2026-08-10 12:18 UTCEG score recompute
  20. 2026-08-10 12:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68348?
CVE-2026-68348 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: ASoC: tas2781: bound firmware description string parsing The TAS2781 firmware parser reads several variable-length description strings with strlen() before checking that the string terminator is present inside the firmware blob. A…
When was CVE-2026-68348 disclosed?
CVE-2026-68348 was first published in the National Vulnerability Database on August 10, 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-68348 actively exploited?
CVE-2026-68348 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 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-68348?
CVE-2026-68348 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68348?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68348, 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-2026-68348

Explore →

Is Your Infrastructure Affected by CVE-2026-68348?

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