Answer in brief
CVE-2025-39869 records a Unknown severity vulnerability in dmaengine: ti: edma: Fix memory allocation size for queue_priority_map. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2025-39869 records a Unknown severity vulnerability in dmaengine: ti: edma: Fix memory allocation size for queue_priority_map. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2b6b3b7420190888793c49e97276e1e73bd7eaed <7d4de60d6db02d9b01d5890d5156b04fad65d07a || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <d722de80ce037dccf6931e778f4a46499d51bdf9 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <301a96cc4dc006c9a285913d301e681cfbf7edb6 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <1baed10553fc8b388351d8fc803e3ae6f1a863bc || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <069fd1688c57c0cc8a3de64d108579b31676f74b || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <d5e82f3f2c918d446df46e8d65f8083fd97cdec5 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <e63419dbf2ceb083c1651852209c7f048089ac0f | 7d4de60d6db02d9b01d5890d5156b04fad65d07a, d722de80ce037dccf6931e778f4a46499d51bdf9, 301a96cc4dc006c9a285913d301e681cfbf7edb6, 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93, 1baed10553fc8b388351d8fc803e3ae6f1a863bc, 069fd1688c57c0cc8a3de64d108579b31676f74b, d5e82f3f2c918d446df46e8d65f8083fd97cdec5, e63419dbf2ceb083c1651852209c7f048089ac0f |
| Linux/Linuxgeneric | 4.4 | Not reported |
Published upstream
Sep 23, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=2b6b3b7420190888793c49e97276e1e73bd7eaed <7d4de60d6db02d9b01d5890d5156b04fad65d07a || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <d722de80ce037dccf6931e778f4a46499d51bdf9 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <301a96cc4dc006c9a285913d301e681cfbf7edb6 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <1baed10553fc8b388351d8fc803e3ae6f1a863bc || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <069fd1688c57c0cc8a3de64d108579b31676f74b || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <d5e82f3f2c918d446df46e8d65f8083fd97cdec5 || >=2b6b3b7420190888793c49e97276e1e73bd7eaed <e63419dbf2ceb083c1651852209c7f048089ac0f | 7d4de60d6db02d9b01d5890d5156b04fad65d07a, d722de80ce037dccf6931e778f4a46499d51bdf9, 301a96cc4dc006c9a285913d301e681cfbf7edb6, 5e462fa0dfdb52b3983cf41532d3d4c7d63e2f93, 1baed10553fc8b388351d8fc803e3ae6f1a863bc, 069fd1688c57c0cc8a3de64d108579b31676f74b, d5e82f3f2c918d446df46e8d65f8083fd97cdec5, e63419dbf2ceb083c1651852209c7f048089ac0f |
| Linux/Linuxgeneric | 4.4 | Not reported |
Published upstream
Sep 23, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
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.
Quoted source text, attributed separately from HOL analysis.