Security Advisory

CVE-2024-53150: Linux USB Audio Out-of-Bounds Read

Last updated:
  • CVE-2024-53150

CVE-2024-53150 is an out-of-bounds read (CWE-125) in the Linux kernel's USB audio driver: it did not check the length of clock descriptors, so a USB device with a short, bogus descriptor can make the kernel read past the buffer. NVD scores it 7.1. CISA lists it as exploited. Fixed in 6.1.120, 5.10.231 and the other stable releases.

Vulnerability summary

CVSS base score

7.1

High severity

EPSS score (FIRST)

1.4%

Probability of exploitation in the wild in the next 30 days

CISA KEV catalog

Yes

Listed as known exploited

Published

Vulnerability ID: CVE-2024-53150 · Source: NVD

Affected components

ComponentCPEVersion range
Linux kernel (ALSA USB audio, CONFIG_SND_USB_AUDIO)cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*Before 5.4.287, 5.5 to before 5.10.231, 5.11 to before 5.15.174, 5.16 to before 6.1.120, 6.2 to before 6.6.64, 6.7 to before 6.11.11, 6.12 to before 6.12.2 (NVD); kernel CNA record: affected from 5.4 and from 4.19.84 in the 4.19 branch with no 4.19 fix listed; unaffected from 6.13
Debian linuxcpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*Fixed in 5.10.234-1 for bullseye (DLA-4075-1), 6.1.123-1 for bookworm, 6.12.3-1 in unstable; linux-6.1 for bullseye fixed in 6.1.128-1~deb11u1 (DLA-4076-1) (Debian security tracker)
Android (kernel, USB subcomponent)—Fixed at security patch level 2025-04-05 or later (Android Security Bulletin April 2025, A-382239029)

What does this mean for affected devices?

CVE-2024-53150 is an out-of-bounds read in the Linux kernel's ALSA USB audio driver, snd-usb-audio. The kernel CNA's record is titled "ALSA: usb-audio: Fix out of bounds reads when finding clock sources" and explains that the driver "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." The fix adds length checks to the validators for clock source, clock multiplier and clock selector descriptors. NVD's Primary score is 7.1, CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H, with CWE-125 (out-of-bounds read). The Linux kernel CNA publishes no CVSS score of its own; CISA's ADP Vulnrichment container gives the same 7.1 vector (NVD, CVE record).

Which kernel versions are affected?

The CVE record marks the bug as introduced in 5.4 and lists the first unaffected release on each stable branch: 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2, and 6.13 onward, where mainline commit a3dd4d63eeb4 landed. The record also marks 4.19.84 and later 4.19 releases, and 5.3.11 and later 5.3 releases, as affected through backports of the original change, and the kernel CNA's dyad file lists no fix commit for either branch. A product on a 4.19 kernel therefore needs a manual backport or a branch change. The dyad file gives the fix commit for each other branch, for example da13ade87a12 for 6.1.120 and 45a92cbc88e4 for 5.10.231.

The only source file the fix touched is sound/usb/clock.c. The sound/usb Makefile builds clock.o into snd-usb-audio and has the line obj-$(CONFIG_SND_USB_AUDIO) += snd-usb-audio.o snd-usbmidi-lib.o, so a firmware image built without CONFIG_SND_USB_AUDIO does not contain the vulnerable code. Our Linux kernel CVE triage guide uses this CVE in its worked example of ruling out kernel CVEs by .config.

Which devices are affected?

Any Linux or Android device that ships the USB audio driver on an unfixed kernel and has a USB host port an attacker can reach. Google's Android Security Bulletin for April 2025, published 7 April 2025, lists CVE-2024-53150 in the Kernel section under the 2025-04-05 security patch level as information disclosure rated High, subcomponent USB (A-382239029); Android devices at patch level 2025-04-05 or later are fixed. Debian, per its security tracker, fixed the linux package in 5.10.234-1 for bullseye (DLA-4075-1), 6.1.123-1 for bookworm and 6.12.3-1 in unstable, and linux-6.1 for bullseye in 6.1.128-1~deb11u1 (DLA-4076-1). No device-maker PSIRT or CISA ICS advisory naming a specific product was found as of 2026-11-19.

How do you fix CVE-2024-53150?

Move the product kernel to at least the fixed release of its stable branch, for example 5.10.231, 5.15.174, 6.1.120 or 6.6.64, or to the latest release of that branch. Where the kernel cannot be rebased, backport the branch's fix commit from the dyad file. If the product does not need USB audio or MIDI, build without CONFIG_SND_USB_AUDIO or remove the snd-usb-audio module, and disable USB host ports customers do not need. The same fixed releases also close CVE-2024-53197, an out-of-bounds access in the same driver.

Is CVE-2024-53150 exploited?

Yes. CISA added it to the KEV catalog on 2025-04-09 with a due date of 2025-04-30, describing an out-of-bounds read "that allows a local, privileged attacker to obtain potentially sensitive information"; known ransomware campaign use is listed as Unknown, as of 2026-11-19 (catalog version 2026.11.18). Google's April 2025 bulletin states "There are indications that the following may be under limited, targeted exploitation" and lists CVE-2024-53150 and CVE-2024-53197. FIRST EPSS gives it 0.01354, the 72.2nd percentile, in the 2026-11-18 dataset (CISA KEV, FIRST EPSS). The same attack class, a malicious USB device feeding bad descriptors to a kernel driver, is behind CVE-2024-53104 in the uvcvideo camera driver, also KEV-listed.

How to fix this class of issueThis advisory's weakness class is Memory corruption. Our practical guide covers how to detect, fix, verify and disclose it: How to fix memory corruption in embedded firmware.

Evidence

  • NVD: status Analyzed; [email protected] Primary CVSS 3.1 7.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H; CISA-ADP Secondary 7.1 same vector; CWE-125; CPE linux_kernel before 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.2, plus debian_linux 11.0; published 2024-12-24; read from cached API response 2026-11-19. — NVD
  • CVE record (CNA Linux, PUBLISHED 2024-12-24): title 'ALSA: usb-audio: Fix out of bounds reads when finding clock sources'; programFiles sound/usb/clock.c; affected from 5.4, plus 4.19.84 to before 4.20 and 5.3.11 to before 5.4; unaffected 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2, 6.13; no CNA CVSS; CISA ADP Vulnrichment 7.1, CWE-125, SSVC exploitation active, technical impact partial. — CVE.org
  • Kernel CNA dyad file: vulnerable since 5.4 (b8e4f1fdfa42); fixed 5.4.287 a632bdcb359f, 5.10.231 45a92cbc88e4, 5.15.174 ab011f7439d9, 6.1.120 da13ade87a12, 6.6.64 74cb86e1006c, 6.11.11 ea0fa76f61cf, 6.12.2 096bb5b43edf, mainline 6.13 a3dd4d63eeb4; 4.19.84 (9feeaa50e5b4) and 5.3.11 (3b17a13b687a) listed with fix 0:0. — Linux kernel vulns.git
  • sound/usb/Makefile: snd-usb-audio-y includes clock.o and quirks.o; obj-$(CONFIG_SND_USB_AUDIO) += snd-usb-audio.o snd-usbmidi-lib.o. — Linux kernel source
  • Android Security Bulletin April 2025 (published 2025-04-07): 'There are indications that the following may be under limited, targeted exploitation': CVE-2024-53150, CVE-2024-53197; CVE-2024-53150 listed under Kernel, 2025-04-05 patch level, A-382239029, ID, High, subcomponent USB. — Android Security Bulletin
  • Debian: linux fixed bullseye 5.10.234-1 (DLA-4075-1), bookworm 6.1.123-1, unstable 6.12.3-1; linux-6.1 bullseye 6.1.128-1~deb11u1 (DLA-4076-1). — Debian security tracker
  • CISA KEV catalog version 2026.11.18: Linux Kernel Out-of-Bounds Read Vulnerability, dateAdded 2025-04-09, dueDate 2025-04-30, knownRansomwareCampaignUse Unknown, local privileged attacker may obtain sensitive information; checked 2026-11-19. — CISA KEV
  • EPSS 0.01354, percentile 0.72154, dataset 2026-11-18, read 2026-11-19. — FIRST EPSS

Related advisories

Sources

  1. NVD
  2. CVE.org record CVE-2024-53150 (CNA: Linux)
  3. Android Security Bulletin: April 2025
  4. Debian security tracker: CVE-2024-53150
  5. Linux kernel vulns.git: CVE-2024-53150.dyad (vulnerable and fixed commits per branch)
  6. Linux kernel source: sound/usb/Makefile
  7. Linux kernel mainline fix commit a3dd4d63eeb4
  8. CISA KEV
  9. FIRST EPSS

Frequently asked questions

Which kernel versions fix CVE-2024-53150?

5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2 and 6.13 onward. Each stable branch has its own fixed release, so a 6.1.120 kernel is fixed even though 6.13 carries the mainline fix (per the kernel CNA's CVE record and dyad file).

Are 4.19 kernels affected by CVE-2024-53150?

The record marks 4.19.84 and later 4.19 releases as affected, because the original change was backported there, and lists no fixed 4.19 release. Devices on 4.19 need a manual backport or a move to a fixed branch (per the kernel CNA's CVE record and dyad file).

Is my firmware affected if it has no USB audio support?

Not if the kernel is built without CONFIG_SND_USB_AUDIO. The only file the fix touched, sound/usb/clock.c, is built into the snd-usb-audio driver only when that option is set (per the CVE record's programFiles and the sound/usb/Makefile).

Which Android security patch level fixes CVE-2024-53150?

Security patch level 2025-04-05 or later. The bulletin lists it as a High-severity information disclosure in the kernel's USB subcomponent and notes indications of limited, targeted exploitation (per the Android Security Bulletin for April 2025).

Is CVE-2024-53150 exploited in the wild?

Yes. CISA added it to the KEV catalog on 2025-04-09, with ransomware use listed as Unknown, as of 2026-11-19 (catalog version 2026.11.18). FIRST EPSS gives it 0.01354, the 72.2nd percentile, in the 2026-11-18 dataset (per CISA KEV and FIRST EPSS).