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: <2024122724-CVE-2024-56532-6931@gregkh>
Date: Fri, 27 Dec 2024 15:11:23 +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-56532: ALSA: us122l: Use snd_card_free_when_closed() at disconnection

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

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

ALSA: us122l: Use snd_card_free_when_closed() at disconnection

The USB disconnect callback is supposed to be short and not too-long
waiting.  OTOH, the current code uses snd_card_free() at
disconnection, but this waits for the close of all used fds, hence it
can take long.  It eventually blocks the upper layer USB ioctls, which
may trigger a soft lockup.

An easy workaround is to replace snd_card_free() with
snd_card_free_when_closed().  This variant returns immediately while
the release of resources is done asynchronously by the card device
release at the last close.

The loop of us122l->mmap_count check is dropped as well.  The check is
useless for the asynchronous operation with *_when_closed().

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


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

	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 4.19.325 with commit 020cbc4d7414f0962004213e2b7bc5cc607e9ec7
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 5.4.287 with commit 75f418b249d84021865eaa59515d3ed9b75ce4d6
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 5.10.231 with commit bf0aa35a7cb8602cccf2387712114e836f65c154
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 5.15.174 with commit 9a48bd2184b142c92a4e17eac074c61fcf975bc9
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 6.1.120 with commit bc778ad3e495333eebda36fe91d5b2c93109cc16
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 6.6.64 with commit 2938dd2648522336133c151dd67bb9bf01cbd390
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 6.11.11 with commit 9b27924dc8d7f8a8c35e521287d4ccb9a006e597
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 6.12.2 with commit 9d5c530e4d70f64b1114f2cc29ac690ba7ac4a38
	Issue introduced in 2.6.28 with commit 030a07e441296c372f946cd4065b5d831d8dc40c and fixed in 6.13-rc1 with commit b7df09bb348016943f56b09dcaafe221e3f73947

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-56532
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/usx2y/us122l.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/020cbc4d7414f0962004213e2b7bc5cc607e9ec7
	https://git.kernel.org/stable/c/75f418b249d84021865eaa59515d3ed9b75ce4d6
	https://git.kernel.org/stable/c/bf0aa35a7cb8602cccf2387712114e836f65c154
	https://git.kernel.org/stable/c/9a48bd2184b142c92a4e17eac074c61fcf975bc9
	https://git.kernel.org/stable/c/bc778ad3e495333eebda36fe91d5b2c93109cc16
	https://git.kernel.org/stable/c/2938dd2648522336133c151dd67bb9bf01cbd390
	https://git.kernel.org/stable/c/9b27924dc8d7f8a8c35e521287d4ccb9a006e597
	https://git.kernel.org/stable/c/9d5c530e4d70f64b1114f2cc29ac690ba7ac4a38
	https://git.kernel.org/stable/c/b7df09bb348016943f56b09dcaafe221e3f73947

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ