# CVE-2025-39869: dmaengine: ti: edma: Fix memory allocation size for queue_priority_map

> A memory allocation bug in the TI EDMA driver causes out-of-bounds writes, leading to kernel crashes on ARM platforms.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2025
- **Updated:** 5 Aug 2026
- **Also known as:** BELL-CVE-2025-39869, DEBIAN-CVE-2025-39869, GHSA-mwhg-gwrr-ff82, ROOT-OS-DEBIAN-11-CVE-2025-39869, ROOT-OS-UBUNTU-2204-CVE-2025-39869, ROOT-OS-UBUNTU-2404-CVE-2025-39869, UBUNTU-CVE-2025-39869

## What is CVE-2025-39869?

CVE-2025-39869 is a high-severity memory corruption vulnerability in Debian Debian Linux, published on 23 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:

dmaengine: ti: edma: Fix memory allocation size for queue_priority_map

Fix a critical memory allocation bug in edma_setup_from_hw() where
queue_priority_map was allocated with insufficient memory. The code
declared queue_priority_map as s8 (*)[2] (pointer to array of 2 s8),
but allocated memory using sizeof(s8) instead of the correct size.

This caused out-of-bounds memory writes when accessing:
  queue_priority_map[i][0] = i;
  queue_priority_map[i][1] = i;

The bug manifested as kernel crashes with "Oops - undefined instruction"
on ARM platforms (BeagleBoard-X15) during EDMA driver probe, as the
memory corruption triggered kernel hardening features on Clang.

Change the allocation to use sizeof(*queue_priority_map) which
automatically gets the correct size for the 2D array structure.

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

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

It affects 2 products.


Products: Debian Debian Linux, Linux kernel.

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

Apply the vendor's patch.

## Is CVE-2025-39869 being exploited?

There is no known exploitation of CVE-2025-39869 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-39869 and fix it if it is affected.

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

## Sources

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

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