Debian LinuxOperating system · Debian
CVE-2024-53150
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix out of bounds reads when finding clock sources 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Linux kernel's ALSA usb-audio driver lacks bLength validation when traversing clock descriptors from USB audio devices. A malicious or malformed USB audio device descriptor with insufficient length causes the driver to read beyond buffer boundaries, leading to out-of-bounds memory access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 11.0
Linux KernelOperating system
< 5.4.287>= 5.5, < 5.10.231>= 5.11, < 5.15.174>= 5.16, < 6.1.120>= 6.2, < 6.6.64>= 6.7, < 6.11.11>= 6.12, < 6.12.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the running kernel versionRun `uname -r` or `cat /proc/version` to obtain the exact kernel version stringAffected if The kernel version falls within any of these ranges: < 5.4.287; >= 5.5 and < 5.10.231; >= 5.11 and < 5.15.174; >= 5.16 and < 6.1.120; >= 6.2 and < 6.6.64; >= 6.7 and < 6.11.11; >= 6.12 and < 6.12.2, or equals 11.0 for Debian Linux
-
Verify the snd-usb-audio kernel module is loadedRun `lsmod | grep snd_usb_audio` or check `/sys/module/snd_usb_audio/version` if availableAffected if The module is loaded and the kernel version is in the affected ranges from step 1
-
Check for connected USB audio devicesRun `lsusb` and look for devices with audio class descriptors, or check `/proc/asound/cards` for USB audio cardsAffected if USB audio devices are connected and the kernel version is in the affected ranges from step 1 - the vulnerability triggers when the kernel processes descriptors from these devices
-
Confirm ALSA USB audio driver support in kernelCheck kernel configuration with `zcat /proc/config.gz 2>/dev/null | grep -i snd_usb_audio` or check `/lib/modules/$(uname -r)/kernel/sound/usb/snd-usb-audio.ko` existsAffected if USB audio support is compiled into the kernel or available as a module and the kernel version is in the affected ranges
A system is affected if it runs a Linux kernel version within the vulnerable ranges AND has the snd-usb-audio driver available, with the risk increasing when untrusted USB audio devices are connected.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.4.2875.10.2315.15.174
Apply the kernel patch to add bLength sanity checks, then rebuild and deploy the updated kernel. Until patched, restrict USB audio device usage to trusted devices only.
Linux Kernel >= 5.4.287, >= 5.10.231, >= 5.15.174, or >= 6.1.120 (depending on branch); Debian 11.0 update via standard apt upgrade
- Identify the currently running Linux kernel version using 'uname -r'
- Determine which major kernel branch your version belongs to (e.g., 5.4.x, 5.10.x, 5.15.x, 6.1.x)
- For Debian 11 (Bullseye), update the kernel package via 'apt update && apt upgrade linux-image-amd64' to obtain a patched kernel
- For other distributions, upgrade to a kernel version >= 5.4.287 if on 5.4.x branch
- If using 5.5-5.10.x branch, upgrade to kernel >= 5.10.231
- If using 5.11-5.15.x branch, upgrade to kernel >= 5.15.174
- If using 5.16-6.1.x branch, upgrade to kernel >= 6.1.120
- Reboot the system to load the patched kernel
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Exploited in the wild — priority engagement
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-53150 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-53150 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data