LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 7.1Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-53150 is a Linux kernel USB-audio bug. A malformed USB audio descriptor can make the driver read past expected memory while finding clock sources. The listed CVSS score is high, and CISA KEV inclusion means known exploitation is recognized, but the bundle does not describe real-world attack details.

Executive priority

Treat this as a high-priority kernel patching item because it is KEV-listed and affects a low-level Linux driver. Urgency is highest for endpoints or shared systems where untrusted USB devices may be connected. The bundle does not support claims of remote exploitation.

Technical view

The ALSA usb-audio driver failed to validate descriptor bLength values during clock descriptor traversal. Short clock source, multiplier, or selector descriptors could trigger out-of-bounds reads. The fix adds sanity checks and skips descriptors shorter than expected. The issue is classified as CWE-125 with CVSS 3.1 score 7.1.

Likely exposure

Exposure is most relevant to Linux systems running affected kernel builds with USB audio support, especially where untrusted or attacker-controlled USB audio devices can be introduced. Distribution kernels may differ, so asset validation should use vendor kernel package advisories and the linked stable fixes.

Exploitation context

CISA KEV is cited for this CVE, so known exploitation should be treated as supported. The provided sources do not explain exploitation method, campaign activity, affected sectors, or whether exploitation requires physical USB access versus another local device path.

Researcher notes

Focus validation on descriptor-length handling in ALSA usb-audio clock descriptor traversal. The affected area is parsing of UAC clock source, multiplier, and selector descriptors. Avoid assuming broader kernel memory corruption beyond the documented out-of-bounds read without additional evidence.

Mitigation direction

  • Apply vendor kernel updates that include the linked stable usb-audio fixes.
  • Prioritize CISA KEV-tracked systems and internet-managed enterprise endpoints.
  • Check Debian and other distribution advisories for fixed kernel package versions.
  • Restrict untrusted USB audio devices where immediate patching is not possible.
  • Reboot systems after kernel update so the fixed kernel is active.

Validation and detection

  • Inventory Linux kernel versions across servers, workstations, and appliances.
  • Confirm whether ALSA usb-audio support is present or loadable.
  • Compare running kernels against distribution advisories and stable fix references.
  • Verify patched systems are booted into the updated kernel.
  • Review endpoint logs for unusual USB audio device activity where available.
Prepared
Confidence
high
Sources
12

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-125: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2024-53150 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.1 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
2ADP providers
12Source links

CISA KEV status

Status
Known exploited
Source
CISA-ADP
Date added
KEV reference

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: activeAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.1CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H1.85.2CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.1High
CVSS 3.1 vector shape for CVE-2024-53150Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. Added to KEVCISA-ADP

    CISA Known Exploited Vulnerabilities metadata lists this CVE as known exploited.

  4. ADP timelineCISA-ADP

    CVE-2024-53150 added to CISA KEV

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvcother:kev
  • 2025-04-09T00:00:00.000Z: CVE-2024-53150 added to CISA KEV
CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a, 9feeaa50e5b4b0b71259d918a36ecf9059e60796, 3b17a13b687ae99939dc94a4ae01fbc34f68deccunaffected
LinuxLinux5.4, 0, 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.64, 6.11.11, 6.12.2, 6.13affected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.