# CVE-2025-38679: media: venus: Fix OOB read due to missing payload bound check

> A missing bounds check in the Linux kernel Venus media driver allows out-of-bounds reads, potentially causing crashes or information leaks.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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:** 4 Sep 2025
- **Updated:** 5 Aug 2026
- **Also known as:** AZL-66863, AZL-73821, BELL-CVE-2025-38679, DEBIAN-CVE-2025-38679, GHSA-5hm5-7p65-wrq6, ROOT-OS-DEBIAN-11-CVE-2025-38679, ROOT-OS-DEBIAN-12-CVE-2025-38679, ROOT-OS-UBUNTU-2204-CVE-2025-38679, ROOT-OS-UBUNTU-2404-CVE-2025-38679, UBUNTU-CVE-2025-38679

## What is CVE-2025-38679?

CVE-2025-38679 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 4 Sep 2025. 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: venus: Fix OOB read due to missing payload bound check

Currently, The event_seq_changed() handler processes a variable number
of properties sent by the firmware. The number of properties is indicated
by the firmware and used to iterate over the payload. However, the
payload size is not being validated against the actual message length.

This can lead to out-of-bounds memory access if the firmware provides a
property count that exceeds the data available in the payload. Such a
condition can result in kernel crashes or potential information leaks if
memory beyond the buffer is accessed.

Fix this by properly validating the remaining size of the payload before
each property access and updating bounds accordingly as properties are
parsed.

This ensures that property parsing is safely bounded within the received
message buffer and protects against malformed or malicious firmware
behavior.

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

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-38679 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-38679 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 4 Sep 2025. 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-38679 in the wild and no public exploit code.

Affected product: Debian Debian 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-38679/ (Markdown: https://insights.sbomify.com/CVE-2025-38679/index.md)
```

## Sources

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

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