Metrics
Affected Vendors & Products
Wed, 01 Oct 2025 21:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Metrics |
ssvc
|
Fri, 19 Sep 2025 16:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-667 | |
CPEs | cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Tue, 04 Mar 2025 15:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-459 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Mon, 30 Dec 2024 01:30:00 +0000
Type | Values Removed | Values Added |
---|---|---|
References |
| |
Metrics |
threat_severity
|
cvssV3_1
|
Fri, 27 Dec 2024 14:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
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. | |
Title | ALSA: usx2y: Use snd_card_free_when_closed() at disconnection | |
References |
|
|

Status: PUBLISHED
Assigner: Linux
Published: 2024-12-27T14:11:16.256Z
Updated: 2025-10-01T20:07:17.451Z
Reserved: 2024-12-27T14:03:05.985Z
Link: CVE-2024-56533

Updated: 2025-10-01T15:40:19.915Z

Status : Modified
Published: 2024-12-27T14:15:32.800
Modified: 2025-10-01T20:17:25.563
Link: CVE-2024-56533
