lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024111955-CVE-2024-50292-e8b6@gregkh>
Date: Tue, 19 Nov 2024 02:32:47 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50292: ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ASoC: stm32: spdifrx: fix dma channel release in stm32_spdifrx_remove

In case of error when requesting ctrl_chan DMA channel, ctrl_chan is not
null. So the release of the dma channel leads to the following issue:
[    4.879000] st,stm32-spdifrx 500d0000.audio-controller:
dma_request_slave_channel error -19
[    4.888975] Unable to handle kernel NULL pointer dereference
at virtual address 000000000000003d
[...]
[    5.096577] Call trace:
[    5.099099]  dma_release_channel+0x24/0x100
[    5.103235]  stm32_spdifrx_remove+0x24/0x60 [snd_soc_stm32_spdifrx]
[    5.109494]  stm32_spdifrx_probe+0x320/0x4c4 [snd_soc_stm32_spdifrx]

To avoid this issue, release channel only if the pointer is valid.

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


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

	Issue introduced in 5.7 with commit 794df9448edb and fixed in 5.10.230 with commit 3a977b554f66
	Issue introduced in 5.7 with commit 794df9448edb and fixed in 5.15.172 with commit 0d75f887aabd
	Issue introduced in 5.7 with commit 794df9448edb and fixed in 6.1.117 with commit 4f1d74f74752
	Issue introduced in 5.7 with commit 794df9448edb and fixed in 6.6.61 with commit 23bdbd1ef3e0
	Issue introduced in 5.7 with commit 794df9448edb and fixed in 6.11.8 with commit 22ae9321054c
	Issue introduced in 5.7 with commit 794df9448edb and fixed in 6.12 with commit 9bb4af400c38

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-50292
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:
	sound/soc/stm/stm32_spdifrx.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/3a977b554f668382dfba31fd62e4cce4fe5643db
	https://git.kernel.org/stable/c/0d75f887aabd80cf37ea48d28f159afa7850ea28
	https://git.kernel.org/stable/c/4f1d74f74752eab8af6b8b28797dc6490d57374c
	https://git.kernel.org/stable/c/23bdbd1ef3e063e03d3c50c15a591b005ebbae39
	https://git.kernel.org/stable/c/22ae9321054cf7f36c537702af133659f51a0b88
	https://git.kernel.org/stable/c/9bb4af400c386374ab1047df44c508512c08c31f

Powered by blists - more mailing lists