CVE-2013-2597
Code Aurora ACDB Audio Driver Stack-based Buffer Overflow Vulnerability
Code Aurora ACDB Audio Driver
Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 15 September 2022. US federal agencies were required to remediate it by 6 October 2022.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 1.5%, which is higher than 74.5% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2013-2597 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2013-2597.
What does CVE-2013-2597 affect?
CVE-2013-2597 affects Code Aurora ACDB Audio Driver. Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Linux kernel 2.6.x and 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, allows attackers to gain privileges via an application that leverages /dev/msm_acdb access and provides a large size value in an ioctl argument.
How severe is CVE-2013-2597?
CVE-2013-2597 is rated HIGH with a CVSS base score of 8.4. EPSS puts the probability of exploitation in the next 30 days at 1.5%, higher than 74.5% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 6 October 2022.
How should organisations respond to CVE-2013-2597?
Apply the vendor patch for Code Aurora ACDB Audio Driver as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.