cve/published/2024/CVE-2024-53239.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-53239: ALSA: 6fire: Release resources at card release

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

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

ALSA: 6fire: Release resources at card release

The current 6fire code tries to release the resources right after the
call of usb6fire_chip_abort().  But at this moment, the card object
might be still in use (as we're calling snd_card_free_when_closed()).

For avoid potential UAFs, move the release of resources to the card's
private_free instead of the manual call of usb6fire_chip_destroy() at
the USB disconnect callback.

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


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

	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 4.19.325 with commit 74357d0b5cd3ef544752bc9f21cbeee4902fae6c
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 5.4.287 with commit 273eec23467dfbfbd0e4c10302579ba441fb1e13
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 5.10.231 with commit f2d06d4e129e2508e356136f99bb20a332ff1a00
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 5.15.174 with commit b889a7d68d7e76b8795b754a75c91a2d561d5e8c
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 6.1.120 with commit ea8cc56db659cf0ae57073e32a4735ead7bd7ee3
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 6.6.64 with commit b754e831a94f82f2593af806741392903f359168
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 6.11.11 with commit 0df7f4b5cc10f5adf98be0845372e9eef7bb5b09
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 6.12.2 with commit 57860a80f03f9dc69a34a5c37b0941ad032a0a8c
	Issue introduced in 2.6.39 with commit c6d43ba816d1cf1d125bfbfc938f2a28a87facf9 and fixed in 6.13 with commit a0810c3d6dd2d29a9b92604d682eacd2902ce947

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-53239
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/usb/6fire/chip.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/74357d0b5cd3ef544752bc9f21cbeee4902fae6c
	https://git.kernel.org/stable/c/273eec23467dfbfbd0e4c10302579ba441fb1e13
	https://git.kernel.org/stable/c/f2d06d4e129e2508e356136f99bb20a332ff1a00
	https://git.kernel.org/stable/c/b889a7d68d7e76b8795b754a75c91a2d561d5e8c
	https://git.kernel.org/stable/c/ea8cc56db659cf0ae57073e32a4735ead7bd7ee3
	https://git.kernel.org/stable/c/b754e831a94f82f2593af806741392903f359168
	https://git.kernel.org/stable/c/0df7f4b5cc10f5adf98be0845372e9eef7bb5b09
	https://git.kernel.org/stable/c/57860a80f03f9dc69a34a5c37b0941ad032a0a8c
	https://git.kernel.org/stable/c/a0810c3d6dd2d29a9b92604d682eacd2902ce947