cve/published/2024/CVE-2024-43856.mbox

From bippy-5f407fcff5a0 Mon Sep 17 00:00:00 2001
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: <linux-cve-announce@vger.kernel.org>
Reply-to: <cve@kernel.org>, <linux-kernel@vger.kernel.org>
Subject: CVE-2024-43856: dma: fix call order in dmam_free_coherent

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

The Linux kernel CVE team has assigned CVE-2024-43856 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 4.19.320 with commit fe2d246080f035e0af5793cb79067ba125e4fb63
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 5.4.282 with commit 2f7bbdc744f2e7051d1cb47c8e082162df1923c9
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 5.10.224 with commit 257193083e8f43907e99ea633820fc2b3bcd24c7
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 5.15.165 with commit 87b34c8c94e29fa01d744e5147697f592998d954
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 6.1.103 with commit f993a4baf6b622232e4c190d34c220179e5d61eb
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 6.6.44 with commit 1fe97f68fce1ba24bf823bfb0eb0956003473130
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 6.10.3 with commit 22094f5f52e7bc16c5bf9613365049383650b02e
	Issue introduced in 2.6.21 with commit 9ac7849e35f705830f7b016ff272b0ff1f7ff759 and fixed in 6.11 with commit 28e8b7406d3a1f5329a03aa25a43aa28e087cb20

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2024-43856
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	kernel/dma/mapping.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	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