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

> A missing bounds check in the TAS2781 firmware parser allows out-of-bounds reads, potentially leading to information disclosure or system crashes.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-68348, DEBIAN-CVE-2026-68348, GHSA-3wp2-xjg2-vxf4, UBUNTU-CVE-2026-68348

## What is CVE-2026-68348?

CVE-2026-68348 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-125 (Out-of-bounds Read)

## Which versions are affected by CVE-2026-68348?


## How do I fix CVE-2026-68348?

Apply the vendor's patch.

## Is CVE-2026-68348 being exploited?

There is no known exploitation of CVE-2026-68348 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68348 and fix it if it is affected.

What it is: CVE-2026-68348 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68348 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68348/ (Markdown: https://insights.sbomify.com/CVE-2026-68348/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68348
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68348
- OSV: https://osv.dev/vulnerability/CVE-2026-68348

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68348/
Summaries are generated and may contain mistakes; the official description above is the record.