Threats / Code Aurora / CVE-2013-2597
CVE-2013-2597
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Code Aurora ACDB Audio Driver vulnerability
Stack-based buffer overflow in Code Aurora ACDB Audio Driver enables privilege escalation. Vulnerability has been exploited in the wild.
Verdict
Today item — known-exploited.
A stack buffer overflow in the ACDB audio driver allows attackers to escalate privileges on affected systems. The vulnerability has demonstrated active exploitation, though ransomware campaigns have not been associated with it.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
1 independent public report 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 2022-09-15).
Probability (EPSS)
EPSS 0.01516 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Code Aurora, ACDB Audio Driver. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — 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 craft malicious input to overflow the stack buffer in the audio driver.
Business
Attacker gains elevated privileges on the device, bypassing security controls.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I leverage the privilege escalation to execute arbitrary code with kernel-level access.
Business
System integrity is compromised; attacker can install persistent malware or access sensitive data.
3
Lateral reach — past segmentation narrative 3
Attacker
I maintain persistence across reboots through kernel-level implants.
Business
Long-term compromise of affected devices creates ongoing operational and data security risk.
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