Skip to main content
CISA Known Exploited Vulnerabilities

Linux Kernel Out-of-Bounds Read Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.

Added to KEV
2025-04-09
Remediation due
2025-04-30

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.

CISA notes
This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. For more information, please see: https://lore.kernel.org/linux-cve-announce/2024122427-CVE-2024-53150-3a7d@gregkh/ ; https://source.android.com/docs/security/bulletin/2025-04-01 ; https://nvd.nist.gov/vuln/detail/CVE-2024-53150

Description

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.

Key Findings

as of 2026-11-22
All KEV statistics→
  • CISA added CVE-2024-53150 to the KEV catalog 106 days after its CVE record was published. The median for entries added in 2025 is 26 days.
  • It is one of 32 Linux Kernel entries in the CISA KEV catalog, and one of 7 added in 2025.
  • Its current EPSS score (1.4%) is higher than that of 3% of CISA KEV entries.

Severity

CVSS 3.1 · CISA · Base score7.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:HOpen in CVSS calculator
SSVC · CISA-ADP
Exploitationactive
Automatableno
Technical impactpartial

Remediation Timeline

BOD 26-04, US federal agencies
Publicly exposed asset
14 days
Asset not publicly exposed
14 days
KEV due date
2025-04-30
21 days after listing

Deadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2025-04-09).

How the timeline is set

Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.

Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.

CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.

Affected Products

ProductAffected versions
Linux
Linux
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <a632bdcb359fd8145e86486ff8612da98e239acd
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <45a92cbc88e4013bfed7fd2ccab3ade45f8e896b
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <ab011f7439d9bbfd34fd3b9cef4b2d6d952c9bb9
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <da13ade87a12dd58829278bc816a61bea06a56a9
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <74cb86e1006c5437b1d90084d22018da30fddc77
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <ea0fa76f61cf8e932d1d26e6193513230816e11d
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <096bb5b43edf755bc4477e64004fa3a20539ec2f
b8e4f1fdfa422398c2d6c47bfb7d1feb3046d70a to <a3dd4d63eeb452cfb064a13862fb376ab108f6a6
9feeaa50e5b4b0b71259d918a36ecf9059e60796
3b17a13b687ae99939dc94a4ae01fbc34f68decc
4.19.84 to <4.20
5.3.11 to <5.4
Linux
Linux
5.4
0 to <5.4 (unaffected)
5.4.287 to 5.4.* (unaffected)
5.10.231 to 5.10.* (unaffected)
5.15.174 to 5.15.* (unaffected)
6.1.120 to 6.1.* (unaffected)
6.6.64 to 6.6.* (unaffected)
6.11.11 to 6.11.* (unaffected)
6.12.2 to 6.12.* (unaffected)
6.13 to * (unaffected)

More from Linux Kernel

All Linux Kernel CVEs→

CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.