---
id: CVE-2024-43856
title: |-
  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 …
summary: |-
  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 …
severity: high
cvss: 7.8
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H'
cwe:
  - CWE-770
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 2.6.21, < 4.19.320'
  - 'linux_kernel >= 4.20, < 5.4.282'
  - 'linux_kernel >= 5.5, < 5.10.224'
  - 'linux_kernel >= 5.11, < 5.15.165'
  - 'linux_kernel >= 5.16, < 6.1.103'
  - 'linux_kernel >= 6.2, < 6.6.44'
  - 'linux_kernel >= 6.7, < 6.10.3'
patched:
  - linux_kernel 6.10.3
published: '2024-08-17'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T01:18:47.923'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-43856'
references:
  - url: 'https://git.kernel.org/stable/c/1fe97f68fce1ba24bf823bfb0eb0956003473130'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/22094f5f52e7bc16c5bf9613365049383650b02e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/257193083e8f43907e99ea633820fc2b3bcd24c7'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/28e8b7406d3a1f5329a03aa25a43aa28e087cb20'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/2f7bbdc744f2e7051d1cb47c8e082162df1923c9'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/87b34c8c94e29fa01d744e5147697f592998d954'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/f993a4baf6b622232e4c190d34c220179e5d61eb'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/fe2d246080f035e0af5793cb79067ba125e4fb63'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00416
epssPercentile: 0.35686
ingestedAt: '2026-10-15T03:30:12.735Z'
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2024-09-10T16:07:08.178694Z'
---

## Overview

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

## Affected

- `linux_kernel >= 2.6.21, < 4.19.320`
- `linux_kernel >= 4.20, < 5.4.282`
- `linux_kernel >= 5.5, < 5.10.224`
- `linux_kernel >= 5.11, < 5.15.165`
- `linux_kernel >= 5.16, < 6.1.103`
- `linux_kernel >= 6.2, < 6.6.44`
- `linux_kernel >= 6.7, < 6.10.3`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.10.3`