| 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-56533: ALSA: usx2y: Use snd_card_free_when_closed() at disconnection |
| |
| Description |
| =========== |
| |
| In the Linux kernel, the following vulnerability has been resolved: |
| |
| ALSA: usx2y: 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 Linux kernel CVE team has assigned CVE-2024-56533 to this issue. |
| |
| |
| Affected and fixed versions |
| =========================== |
| |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 5.10.231 with commit 24fe9f7ca83ec9acf765339054951f5cd9ae5c5d |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 5.15.174 with commit befcca1777525e37c659b4129d8ac7463b07ef67 |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 6.1.120 with commit 7bd8838c0ea886679a32834fdcacab296d072fbe |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 6.6.64 with commit e07605d855c4104d981653146a330ea48f6266ed |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 6.11.11 with commit ffbfc6c4330fc233698529656798bee44fea96f5 |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 6.12.2 with commit e869642a77a9b3b98b0ab2c8fec7af4385140909 |
| Issue introduced in 2.6.13 with commit 230cd5e24853ed4dd960461989b8ed0986d37a99 and fixed in 6.13 with commit dafb28f02be407e07a6f679e922a626592b481b0 |
| |
| 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-56533 |
| 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/usbusx2y.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/24fe9f7ca83ec9acf765339054951f5cd9ae5c5d |
| https://git.kernel.org/stable/c/befcca1777525e37c659b4129d8ac7463b07ef67 |
| https://git.kernel.org/stable/c/7bd8838c0ea886679a32834fdcacab296d072fbe |
| https://git.kernel.org/stable/c/e07605d855c4104d981653146a330ea48f6266ed |
| https://git.kernel.org/stable/c/ffbfc6c4330fc233698529656798bee44fea96f5 |
| https://git.kernel.org/stable/c/e869642a77a9b3b98b0ab2c8fec7af4385140909 |
| https://git.kernel.org/stable/c/dafb28f02be407e07a6f679e922a626592b481b0 |
