data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2024-53150 in the interactive tracker

CVE-2024-53150

ALSA: usb-audio: Fix out of bounds reads when finding clock sources

KEV EPSS 1.4%

Published 2024-12-24 (22 months ago) by the Linux kernel CNA. Subsystem sound/usb. Debian urgency: not yet assigned.

What to do, per Debian release

Debian's own status for CVE-2024-53150 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormfixed6.1.123-1Update the kernel and reboot. Fixed in 6.1.123-1. A running kernel keeps the old code until the machine restarts.
Debian 13trixiefixed6.12.3-1Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts.
Debian 14forkyfixed6.12.3-1Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed6.12.3-1Update the kernel and reboot. Fixed in 6.12.3-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

The current USB-audio driver code doesn't check bLength of each descriptor at traversing for clock descriptors. That is, when a device provides a bogus descriptor with a shorter bLength, the driver might hit out-of-bounds reads. For addressing it, this patch adds sanity checks to the validator functions for the clock descriptor traversal. When the descriptor length is shorter than expected, it's skipped in the loop. For the clock source and clock multiplier descriptors, we can just check bLength against the sizeof() of each descriptor type. OTOH, the clock selector descriptor of UAC2 and UAC3 has an array of bNrInPins elements and two more fields at its tail, hence those have to be checked in addition to the sizeof() check.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

sound/usb/clock.c

What this is
SOUNDMAINTAINERS section matched on sound/ · linux-sound@vger.kernel.org · Maintained
Kernel module
snd_usb_audio

Check it on the machine

grep -wE 'CONFIG_SND|CONFIG_SND_USB_AUDIO' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

lsmod | grep -w snd_usb_audio

Prints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.

Show whether Debian builds this, per release

Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.

  • bookworm, trixie, forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64
M
a module where it is built at all; some flavours do not build it
Build switches
CONFIG_SND, CONFIG_SND_USB_AUDIO
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Known to be exploited in the wild

Added to KEV
2025-04-09
Federal due date
2025-04-30
Ransomware use
unknown
Required action
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

the KEV catalogue

Signals

Published
2024-12-24 (22 months ago)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
1.35%, higher than 71.1% of all CVEssource
CISA KEV
listedthe KEV catalogue
Debian urgency
not yet assignedsource
Subsystem
sound/usb

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
5.45.4.287a632bdcb359f
5.45.10.23145a92cbc88e4
5.45.15.174ab011f7439d9
5.46.1.120da13ade87a12
5.46.6.6474cb86e1006c
5.46.11.11ea0fa76f61cf
5.46.12.2096bb5b43edf
5.46.13a3dd4d63eeb4
4.19.8400
5.3.1100

Debian advisories

AdvisoryDateShipped toDebian
DLA-4076-12025-03-01bullseye 6.1.128-1~deb11u1tracker
DLA-4075-12025-03-01bullseye 5.10.234-1tracker

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2024-53150, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.