LiveActive security incident?Get immediate response
CVE Record

CVE-2013-2597: Stack-based buffer overflow in the acdb_ioctl function in audio_acdb.c in the acdb audio driver for the Lin...

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.

HighCVSS 8.4Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2013-2597 is an older Android/Linux kernel driver flaw affecting Qualcomm MSM audio components. A malicious local app could abuse the vulnerable audio driver to gain high privileges on the device. CISA lists it as known exploited, so legacy or unsupported Android devices deserve urgent review.

Executive priority

Treat this as a high-priority legacy-device exposure issue. Active exploitation is documented through CISA KEV, and successful abuse could compromise device confidentiality, integrity, and availability. Priority depends on whether affected Qualcomm MSM Android devices remain in use.

Technical view

The issue is a stack-based buffer overflow in acdb_ioctl in audio_acdb.c, in the acdb audio driver for Linux kernel 2.6.x and 3.x as used in QuIC Android contributions for MSM devices. The described trigger involves /dev/msm_acdb access and an oversized ioctl argument.

Likely exposure

Exposure is most likely on legacy Android devices or embedded products using Qualcomm MSM kernels with the affected acdb audio driver. The source bundle does not identify exact vendors, models, firmware builds, or package versions.

Exploitation context

CISA KEV status supports active exploitation. The source bundle describes local app-based privilege gain, not remote exploitation. No cited source in the bundle provides safe details on exploit prevalence, malware families, or observed targeting.

Researcher notes

The public bundle gives a clear vulnerable function, driver, weakness class, and access path, but affected product metadata is incomplete. Avoid broad product claims without OEM firmware evidence. Validation should focus on kernel lineage, driver presence, device node exposure, and vendor patch status.

Mitigation direction

  • Inventory Android and embedded devices using Qualcomm MSM kernels.
  • Check OEM, Qualcomm, or CodeAurora guidance for fixed firmware or kernels.
  • Apply confirmed vendor firmware or OS updates where available.
  • Restrict untrusted app installation on potentially affected legacy devices.
  • Retire unsupported devices when no vendor remediation is available.

Validation and detection

  • Identify devices running Linux kernel 2.6.x or 3.x with Qualcomm MSM components.
  • Check whether the acdb audio driver and /dev/msm_acdb are present.
  • Confirm firmware or kernel build status against vendor guidance.
  • Review mobile telemetry for suspicious local privilege escalation indicators.
  • Track remediation as KEV-driven risk until affected assets are cleared.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-121: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2013-2597 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.4 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.4CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H2.55.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.4High
CVSS 3.1 vector shape for CVE-2013-2597Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.