Threats / Linux / CVE-2024-53197
CVE-2024-53197
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Linux Kernel vulnerability
Linux Kernel USB-audio driver contains an out-of-bounds write vulnerability allowing physical attackers with malicious USB devices to manipulate memory, escalate privileges, or execute arbitrary code.
Verdict
Today item — known-exploited.
An attacker with physical access can exploit this out-of-bounds access flaw via a crafted USB device to gain kernel-level code execution and full system compromise. Exploitation has been observed in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
6 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-04-09).
Probability (EPSS)
EPSS 0.03558 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Linux, Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I connect a malicious USB audio device to the target system.
Business
The organization loses physical security assurance for connected devices.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I trigger out-of-bounds memory access in the USB-audio driver through device interaction.
Business
System stability is compromised and kernel memory becomes corrupted.
3
Lateral reach — past segmentation narrative 3
Attacker
I write to kernel memory to overwrite privilege structures or inject code.
Business
Privilege escalation occurs, elevating the attacker from user to kernel level.
4
Data at risk — exfiltration narrative 4
Attacker
I execute arbitrary code with kernel privileges to establish persistence or exfiltrate data.
Business
Complete system compromise enables data theft, malware installation, and loss of confidentiality and integrity.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05