CVE-2024-53197
CVE-2024-53197 is a security flaw in Linux Kernel, the core of Linux, which runs most servers, Android phones and many home routers. Attackers can run their own code on Linux Kernel. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of flaws known to be used in attacks on 9 Apr 2025.[1]
Linux Kernel is business software or equipment. Most families won’t have it, but attackers break into it to get inside companies, and from there to what those companies hold about their customers, patients and staff. Fixed by 8 commits to Linux, in the releases that include them.
Description
CISA calls it an out-of-bounds access in Linux Kernel. In its words: “Linux Kernel contains an out-of-bounds access vulnerability in the USB-audio driver that allows an attacker with physical access to the system to use a malicious USB device to potentially manipulate system memory, escalate privileges, or execute arbitrary code.”[1]
The CVE record adds: “In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devices A bogus device can provide a bNumConfigurations value that exceeds the initial value used in usb_get_configuration for allocating dev->config. This can lead to out-of-bounds accesses later, e.g. in usb_destroy_configuration.”[2]
The underlying weakness is out-of-bounds write (CWE-787), in MITRE’s list of common software weaknesses.
It scores 7.8 out of 10 on the Common Vulnerability Scoring System, which rates it high, scored by the organisation that published the CVE using CVSS 3.1.[2]
Affected versions
NVD’s record lists these fixed versions: in each line, everything before the version shown is affected.[2]
| Product | Fixed in |
|---|---|
| Linux | commit 0b4ea4bfe165 |
| Linux | commit 9b8460a2a7ce |
| Linux | commit 62dc01c83fa7 |
| Linux | commit 9887d859cd60 |
| Linux | commit 920a369a9f01 |
| Linux | commit b8f8b81dabe5 |
| Linux | commit 379d3b9799d9 |
| Linux | commit b521b53ac6eb |
Most families won’t have Linux Kernel; it’s for whoever looks after IT at work.
Exploitation
CISA added it to its catalog of known exploited vulnerabilities on 9 Apr 2025, 103 days after it was made public. CISA lists a flaw only when it has reliable evidence of it being exploited, and gave US federal agencies until 30 Apr 2025 to fix it.[1]
FIRST’s Exploit Prediction Scoring System, which estimates how likely a flaw is to be used in attacks in the next 30 days from what it sees across the internet, puts it at 4%. That’s in the top 10% of the flaws it scores.[4]
CISA assesses it as not automatable: each attack takes some work.
CISA doesn’t say who was attacked, or how.
Fix
Linux has published a fix or advice.[3] CISA’s 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.”[1]
- Check whether you use it.Linux Kernel is business software or equipment, so most families won’t have it. If you run a business, or work from home on company equipment, ask whoever looks after your IT.
- Send this page to your IT person.Ask them to confirm it’s fixed (fixed by 8 commits to Linux, in the releases that include them), or not in use. CISA gave US government agencies until 30 Apr 2025 to fix it.
- If it can’t be fixed, take it offline.CISA’s advice when there’s no fix is to stop using the product, or take it off the internet, until there is one.
You can’t fix someone else’s server, but you can watch for what follows a break-in like this: a breach notice, a password reset you didn’t ask for, or a scam message that knows things it shouldn’t. HARD watches for those for you and your family.
Timeline
| Date | Event |
|---|---|
| The flaw is made public in the National Vulnerability Database, with a severity score of 7.8.[2] | |
| CISA adds it to its catalog of flaws known to be used in attacks.[1] | |
| CISA’s deadline for US government agencies to fix it.[1] | |
| FIRST puts the odds of it being used in attacks in the next 30 days at 4%.[4] |
See also
Other Linux Kernel flaws
- CVE-2026-46300: missing initialization of a variable ·
- CVE-2026-53266: out-of-bounds write ·
- CVE-2025-39964: race condition ·
- CVE-2025-39682: improper check for unusual or exceptional conditions ·
- CVE-2026-53362: unspecified ·
- CVE-2022-0995: out-of-bounds write ·
Other out-of-bounds write flaws
- CVE-2026-86950, Apple devices: out-of-bounds write ·
- CVE-2026-87491, Chrome and other Chromium browsers: out of bounds write ·
- CVE-2026-11645, Chrome and other Chromium browsers: out-of-bounds read and write ·
- CVE-2026-0300, Palo Alto Networks PAN-OS: out-of-bounds write ·
- CVE-2026-3909, Google Skia: out-of-bounds write ·
Added the same day
- CVE-2024-53150, Linux Kernel: out-of-bounds read ·
Every Linux flaw on CISA’s list · Everything added in April 2025
References
- ^ Cybersecurity and Infrastructure Security Agency. “Linux Kernel Out-of-Bounds Access Vulnerability”. Known Exploited Vulnerabilities Catalog, added 9 Apr 2025.
- ^ National Institute of Standards and Technology. “CVE-2024-53197 Detail”. National Vulnerability Database, published 27 Dec 2024.
- ^ Linux. Advisories and fixes: lore.kernel.org, source.android.com, git.kernel.org, git.kernel.org, git.kernel.org, and 3 more on NVD’s record.
- ^ FIRST. “Exploit Prediction Scoring System”. EPSS 0.041, percentile 90.8, 31 Oct 2026.
- CVE Program. “CVE-2024-53197”. The official CVE record.
This article is built from CISA’s catalog (version 2026.10.30), NVD’s record and FIRST’s scores, kept in HARD’s database and checked every morning. The plain English is HARD’s.