Linux Kernel up to 6.17-rc5 dmaengine edma_setup_from_hw memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Linux Kernel up to 6.1.152/6.6.106/6.12.47/6.16.7/6.17-rc5. This vulnerability affects the function edma_setup_from_hw of the component dmaengine. Performing a manipulation results in memory corruption.
This vulnerability is identified as CVE-2025-39869. There is not any exploit available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Linux Kernel up to 6.1.152/6.6.106/6.12.47/6.16.7/6.17-rc5. It has been classified as critical. This affects the function edma_setup_from_hw of the component dmaengine. The manipulation with an unknown input leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at git.kernel.org. This vulnerability is uniquely identified as CVE-2025-39869 since 04/16/2025. The exploitability is told to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/16/2026).
The vulnerability scanner Nessus provides a plugin with the ID 265863 (Linux Distros Unpatched Vulnerability : CVE-2025-39869), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 6.1.153, 6.6.107, 6.12.48, 6.16.8 or 6.17-rc6 eliminates this vulnerability. Applying the patch 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93/1baed10553fc8b388351d8fc803e3ae6f1a863bc/069fd1688c57c0cc8a3de64d108579b31676f74b/d5e82f3f2c918d446df46e8d65f8083fd97cdec5/e63419dbf2ceb083c1651852209c7f048089ac0f is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (265863) and CERT Bund (WID-SEC-2025-2107). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Container-Optimized OS
- Debian Linux
- Amazon Linux 2
- Red Hat Enterprise Linux
- Ubuntu Linux
- SUSE Linux
- Oracle Linux
- SUSE openSUSE
- Open Source Linux Kernel
- RESF Rocky Linux
- Dell Secure Connect Gateway
- IBM QRadar SIEM
- Dell NetWorker
Product
Type
Vendor
Name
Version
- 6.1.152
- 6.6.106
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.12.44
- 6.12.45
- 6.12.46
- 6.12.47
- 6.16.0
- 6.16.1
- 6.16.2
- 6.16.3
- 6.16.4
- 6.16.5
- 6.16.6
- 6.16.7
- 6.17-rc1
- 6.17-rc2
- 6.17-rc3
- 6.17-rc4
- 6.17-rc5
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 7.1
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 265863
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-39869
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.153/6.6.107/6.12.48/6.16.8/6.17-rc6
Patch: 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93/1baed10553fc8b388351d8fc803e3ae6f1a863bc/069fd1688c57c0cc8a3de64d108579b31676f74b/d5e82f3f2c918d446df46e8d65f8083fd97cdec5/e63419dbf2ceb083c1651852209c7f048089ac0f
Timeline
04/16/2025 CVE reserved09/23/2025 Advisory disclosed
09/23/2025 VulDB entry created
02/16/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2025-39869 (🔒)
GCVE (CVE): GCVE-0-2025-39869
GCVE (VulDB): GCVE-100-325581
CERT Bund: WID-SEC-2025-2107 - Linux Kernel: Mehrere Schwachstellen
Entry
Created: 09/23/2025 08:27Updated: 02/16/2026 07:56
Changes: 09/23/2025 08:27 (59), 09/28/2025 21:40 (2), 11/28/2025 07:14 (7), 01/12/2026 03:18 (1), 01/21/2026 01:40 (11), 02/09/2026 06:32 (1), 02/16/2026 07:56 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.