Answer in brief
CVE-2024-40970 records a Unknown severity vulnerability in Avoid hw_desc array overrun in dw-axi-dmac. 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 | >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <7c3bb96a20cd8db3b8824b2ff08b6cde4505c7e5 || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <dd42570018f5962c10f215ad9c21274ed5d3541e || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <e151ae1ee065cf4b8ce4394ddb9d9c8df6370c66 || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <9004784e8d68bcd1ac1376407ba296fa28f04dbe || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <333e11bf47fa8d477db90e2900b1ed3c9ae9b697 | 7c3bb96a20cd8db3b8824b2ff08b6cde4505c7e5, dd42570018f5962c10f215ad9c21274ed5d3541e, e151ae1ee065cf4b8ce4394ddb9d9c8df6370c66, 9004784e8d68bcd1ac1376407ba296fa28f04dbe, 333e11bf47fa8d477db90e2900b1ed3c9ae9b697 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Jul 12, 2024
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: Avoid hw_desc array overrun in dw-axi-dmac I have a use case where nr_buffers = 3 and in which each descriptor is composed by 3 segments, resulting in the DMA channel descs_allocated to be 9. Since axi_desc_put() handles the hw_desc considering the descs_allocated, this scenario would result in a kernel panic (hw_desc array will be overrun). To fix this, the proposal is to add a new member to the axi_dma_desc structure, where we keep the number of allocated hw_descs (axi_desc_alloc()) and use it in axi_desc_put() to handle the hw_desc array correctly. Additionally I propose to remove the axi_chan_start_first_queued() call after completing the transfer, since it was identified that unbalance can occur (started descriptors can be interrupted and transfer ignored due to DMA channel not being enabled).
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-40970 records a Unknown severity vulnerability in Avoid hw_desc array overrun in dw-axi-dmac. 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 | >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <7c3bb96a20cd8db3b8824b2ff08b6cde4505c7e5 || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <dd42570018f5962c10f215ad9c21274ed5d3541e || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <e151ae1ee065cf4b8ce4394ddb9d9c8df6370c66 || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <9004784e8d68bcd1ac1376407ba296fa28f04dbe || >=ef6fb2d6f1abd56cc067c694253ea362159b5ac3 <333e11bf47fa8d477db90e2900b1ed3c9ae9b697 | 7c3bb96a20cd8db3b8824b2ff08b6cde4505c7e5, dd42570018f5962c10f215ad9c21274ed5d3541e, e151ae1ee065cf4b8ce4394ddb9d9c8df6370c66, 9004784e8d68bcd1ac1376407ba296fa28f04dbe, 333e11bf47fa8d477db90e2900b1ed3c9ae9b697 |
| Linux/Linuxgeneric | 5.12 | Not reported |
Published upstream
Jul 12, 2024
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: Avoid hw_desc array overrun in dw-axi-dmac I have a use case where nr_buffers = 3 and in which each descriptor is composed by 3 segments, resulting in the DMA channel descs_allocated to be 9. Since axi_desc_put() handles the hw_desc considering the descs_allocated, this scenario would result in a kernel panic (hw_desc array will be overrun). To fix this, the proposal is to add a new member to the axi_dma_desc structure, where we keep the number of allocated hw_descs (axi_desc_alloc()) and use it in axi_desc_put() to handle the hw_desc array correctly. Additionally I propose to remove the axi_chan_start_first_queued() call after completing the transfer, since it was identified that unbalance can occur (started descriptors can be interrupted and transfer ignored due to DMA channel not being enabled).
Quoted source text, attributed separately from HOL analysis.