Skip to content
vulnerability

CVE-2024-53150

7.1
High
KEV · Exploited in wildEPSS 1%Patch available

In 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.

exploited
Yes, in CISA KEV since 9 Apr 2025fix by 30 Apr 2025 (CISA deadline for US federal agencies)
fix
Fixed in < 5.4, >= 5.4.287 and <= 5.4.*, >= 5.10.231 and <= 5.10.* +6
likelihood
EPSS 1.4%
Published 24 Dec 2024Analysed here 2 Nov 2026CVSS scored by CISA

do firstUpgrade to a fixed release: < 5.4, >= 5.4.287 and <= 5.4.*, >= 5.10.231 and <= 5.10.*, >= 5.15.174 and <= 5.15.* (+5 more below).

triage
server-sideruntimeWAF can block: noAV · localCWE-125· Out-of-Bounds Read

Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.

Also consider: patch

Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectorlocalattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegritynoneavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
common questions

Is CVE-2024-53150 being exploited?

Yes. CVE-2024-53150 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2024-53150?

CVE-2024-53150 is rated High with a CVSS score of 7.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2024-53150?

Yes. A fix has been recorded for CVE-2024-53150. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2024-53150 affect?

CVE-2024-53150 affects debian:debian_linux, linux:linux_kernel. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
debian:debian_linuxlinux:linux_kernel
affected versions
Linux
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < a632bdcb359fd8145e86486ff8612da98e239acd
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < 45a92cbc88e4013bfed7fd2ccab3ade45f8e896b
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < ab011f7439d9bbfd34fd3b9cef4b2d6d952c9bb9
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < da13ade87a12dd58829278bc816a61bea06a56a9
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < 74cb86e1006c5437b1d90084d22018da30fddc77
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < ea0fa76f61cf8e932d1d26e6193513230816e11d
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < 096bb5b43edf755bc4477e64004fa3a20539ec2f
  • affected>= b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a and < a3dd4d63eeb452cfb064a13862fb376ab108f6a6
  • affected9feeaa50e5b4b0b71259d918a36ecf9059e60796
  • affected3b17a13b687ae99939dc94a4ae01fbc34f68decc
  • affected>= 4.19.84 and < 4.20
  • affected>= 5.3.11 and < 5.4
  • affected5.4
vendor says fixed in< 5.4, >= 5.4.287 and <= 5.4.*, >= 5.10.231 and <= 5.10.*, >= 5.15.174 and <= 5.15.*, >= 6.1.120 and <= 6.1.*, >= 6.6.64 and <= 6.6.*, >= 6.11.11 and <= 6.11.*, >= 6.12.2 and <= 6.12.*, >= 6.13 and <= *

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

cisa ssvc

exploitation
active
automatable
no
technical impact
partial

Assessed by CISA 9 Apr 2025 (SSVC 2.0.3).

timeline

  1. 24 Dec 2024Published
  2. 9 Apr 2025Added to CISA KEV (exploited in the wild) · 105 days (about 4 months) later
  3. 9 Apr 2025CISA SSVC assessment: exploitation active · 1 day later
  4. 30 Apr 2025CISA remediation due date (US federal agencies) · 20 days later
  5. 23 May 2026CVE record last updated · 389 days (about 1 year) later
  6. 2 Nov 2026Analysed by vulneraibility.com · 163 days (about 5 months) later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
11 references in the CVE record: 11 links
Show 3 more
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-53150
  • Linklists.debian.org /debian-lts-announce/2025/03/msg00001.html
  • Linklists.debian.org /debian-lts-announce/2025/03/msg00002.html

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved