Actively exploited

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

Linux Kernel contains an out-of-bounds read vulnerability in the USB-audio driver that allows a local, privileged attacker to obtain potentially sensitive information.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 9 Apr 2025.
  • Rated High severity (CVSS 7.1, scored by CISA).
  • It has been in the catalogue for 576 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

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.

Affected Versions

ProductVersions
Linux Linuxb8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before a632bdcb359fd8145e86486ff8612da98e239acd
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before 45a92cbc88e4013bfed7fd2ccab3ade45f8e896b
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before ab011f7439d9bbfd34fd3b9cef4b2d6d952c9bb9
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before da13ade87a12dd58829278bc816a61bea06a56a9
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before 74cb86e1006c5437b1d90084d22018da30fddc77
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to before ea0fa76f61cf8e932d1d26e6193513230816e11d
Linux Linux5.4

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Linux Kernel. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2024-53150 and every other exploited flaw on the list.

Check My Exposure