CVERadar
HIGH · CVSS 3.1 7.1CISA KEV · added 2025-04-09EPSS 1.35% (p71)Threat level 51

CVE-2024-53150: Linux Kernel Out-of-Bounds Read Vulnerability

Linux · Kernel · NVD published 2024-12-24 · posted 2025-04-09 · last modified 2026-06-17

What it is

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.

WeaknessCWE-125
CVSS vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H (source: [email protected])
CISA due date2025-04-30 (for US federal agencies under BOD; a good deadline for everyone)
ATT&CK tacticsInitial Access → Lateral Movement → Collection → Exfiltration

Exploitation evidence

First exploit evidence seen: 2025-04-09 (earliest date across the sources below).

Exploited in the wild

  • CISA KEV: listed since 2025-04-09. Source

Sources: CISA KEV.

Defend the Chain

The attack chain for CVE-2024-53150 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 51/100
Defender level 1 · 0 XP
Chain links broken: 0/3

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Stealth

Defense Impairment

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1091 Replication Through Removable Media CTID: exploitation technique

By crafting a malicious USB audio device, an attacker can trigger an out-of-bounds read error in the kernel, potentially exposing sensitive kernel information.

How to fix it

CISA 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. (source: CISA KEV)

Fixed versions

  • linux linux kernel: upgrade to 5.4.287 or later
  • linux linux kernel: upgrade to 5.10.231 or later (affected from 5.5)
  • linux linux kernel: upgrade to 5.15.174 or later (affected from 5.11)
  • linux linux kernel: upgrade to 6.1.120 or later (affected from 5.16)
  • linux linux kernel: upgrade to 6.6.64 or later (affected from 6.2)
  • linux linux kernel: upgrade to 6.11.11 or later (affected from 6.7)
  • linux linux kernel: upgrade to 6.12.2 or later (affected from 6.12)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

MITRE ATT&CK mitigations for this chain

Detection Generic guidance

  • Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
  • Lateral Movement: Watch for the compromised host authenticating to other internal systems it does not normally talk to.
  • Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.
  • Exfiltration: Watch for large or unusual outbound transfers from the affected host.

Response checklist Generic guidance

  1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
  2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
  3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
  4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

Sources