# CVE-2025-68819: media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()

> A missing bounds check in the dtv5100 USB driver allows out-of-bounds memory access, potentially leading to code execution or system crashes.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 13 Jan 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2025-68819, DEBIAN-CVE-2025-68819, GHSA-7rq6-3vvj-vpcc, ROOT-OS-DEBIAN-11-CVE-2025-68819, ROOT-OS-DEBIAN-12-CVE-2025-68819, ROOT-OS-DEBIAN-13-CVE-2025-68819, ROOT-OS-UBUNTU-2204-CVE-2025-68819, ROOT-OS-UBUNTU-2404-CVE-2025-68819, UBUNTU-CVE-2025-68819

## What is CVE-2025-68819?

CVE-2025-68819 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 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:

media: dvb-usb: dtv5100: fix out-of-bounds in dtv5100_i2c_msg()

rlen value is a user-controlled value, but dtv5100_i2c_msg() does not
check the size of the rlen value. Therefore, if it is set to a value
larger than sizeof(st->data), an out-of-bounds vuln occurs for st->data.

Therefore, we need to add proper range checking to prevent this vuln.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2025-68819?


## How do I fix CVE-2025-68819?

Apply the vendor's patch.

## Is CVE-2025-68819 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68819 and fix it if it is affected.

What it is: CVE-2025-68819 is a high-severity memory corruption vulnerability in Linux, published on 13 Jan 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-2025-68819 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-2025-68819/ (Markdown: https://insights.sbomify.com/CVE-2025-68819/index.md)
```

## Sources

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

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