Answer in brief
CVE-2024-43856 records a Unknown severity vulnerability in dma: fix call order in dmam_free_coherent. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (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-2024-43856 records a Unknown severity vulnerability in dma: fix call order in dmam_free_coherent. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (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), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <fe2d246080f035e0af5793cb79067ba125e4fb63 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <2f7bbdc744f2e7051d1cb47c8e082162df1923c9 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <257193083e8f43907e99ea633820fc2b3bcd24c7 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <87b34c8c94e29fa01d744e5147697f592998d954 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <f993a4baf6b622232e4c190d34c220179e5d61eb || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <1fe97f68fce1ba24bf823bfb0eb0956003473130 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <22094f5f52e7bc16c5bf9613365049383650b02e || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <28e8b7406d3a1f5329a03aa25a43aa28e087cb20 | fe2d246080f035e0af5793cb79067ba125e4fb63, 2f7bbdc744f2e7051d1cb47c8e082162df1923c9, 257193083e8f43907e99ea633820fc2b3bcd24c7, 87b34c8c94e29fa01d744e5147697f592998d954, f993a4baf6b622232e4c190d34c220179e5d61eb, 1fe97f68fce1ba24bf823bfb0eb0956003473130, 22094f5f52e7bc16c5bf9613365049383650b02e, 28e8b7406d3a1f5329a03aa25a43aa28e087cb20 |
| Linux/Linuxgeneric | 2.6.21 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
Aug 17, 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: dma: fix call order in dmam_free_coherent dmam_free_coherent() frees a DMA allocation, which makes the freed vaddr available for reuse, then calls devres_destroy() to remove and free the data structure used to track the DMA allocation. Between the two calls, it is possible for a concurrent task to make an allocation with the same vaddr and add it to the devres list. If this happens, there will be two entries in the devres list with the same vaddr and devres_destroy() can free the wrong entry, triggering the WARN_ON() in dmam_match. Fix by destroying the devres entry before freeing the DMA allocation. kokonut //net/encryption http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03
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), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <fe2d246080f035e0af5793cb79067ba125e4fb63 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <2f7bbdc744f2e7051d1cb47c8e082162df1923c9 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <257193083e8f43907e99ea633820fc2b3bcd24c7 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <87b34c8c94e29fa01d744e5147697f592998d954 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <f993a4baf6b622232e4c190d34c220179e5d61eb || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <1fe97f68fce1ba24bf823bfb0eb0956003473130 || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <22094f5f52e7bc16c5bf9613365049383650b02e || >=9ac7849e35f705830f7b016ff272b0ff1f7ff759 <28e8b7406d3a1f5329a03aa25a43aa28e087cb20 | fe2d246080f035e0af5793cb79067ba125e4fb63, 2f7bbdc744f2e7051d1cb47c8e082162df1923c9, 257193083e8f43907e99ea633820fc2b3bcd24c7, 87b34c8c94e29fa01d744e5147697f592998d954, f993a4baf6b622232e4c190d34c220179e5d61eb, 1fe97f68fce1ba24bf823bfb0eb0956003473130, 22094f5f52e7bc16c5bf9613365049383650b02e, 28e8b7406d3a1f5329a03aa25a43aa28e087cb20 |
| Linux/Linuxgeneric | 2.6.21 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
Aug 17, 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: dma: fix call order in dmam_free_coherent dmam_free_coherent() frees a DMA allocation, which makes the freed vaddr available for reuse, then calls devres_destroy() to remove and free the data structure used to track the DMA allocation. Between the two calls, it is possible for a concurrent task to make an allocation with the same vaddr and add it to the devres list. If this happens, there will be two entries in the devres list with the same vaddr and devres_destroy() can free the wrong entry, triggering the WARN_ON() in dmam_match. Fix by destroying the devres entry before freeing the DMA allocation. kokonut //net/encryption http://sponge2/b9145fe6-0f72-4325-ac2f-a84d81075b03
Quoted source text, attributed separately from HOL analysis.