dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2025-32061

HIGH · 8.8 CVSS v3.1 Published 2026-02-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The specific flaw exists within the Bluetooth stack developed by Alps Alpine of the Infotainment ECU manufactured by Bosch. The issue results from the lack of proper boundary validation of user-supplied data, which can result in a stack-based buffer overflow when receiving a specific packet on the established upper layer L2CAP channel. An attacker can leverage this vulnerability to obtain remote code execution on the Infotainment ECU with root privileges. First identified on Nissan Leaf ZE1 manufactured in 2020.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stack-based buffer overflow in Alps Alpine's Bluetooth stack within Bosch Infotainment ECU. The vulnerability stems from insufficient boundary validation of user-supplied data in L2CAP channel processing, allowing remote attackers to achieve root-level code execution via specially crafted packets.

MitigationVendor-supplied firmware update for the Infotainment ECU is required. Until patch availability, disable Bluetooth functionality on affected vehicles and limit ECU network exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Bosch Infotainment ECU in use
    Locate the ECU hardware identifier or firmware banner on the infotainment system. Check vehicle service documentation or ECU diagnostic interface for the model number and confirm it uses an Alps Alpine Bluetooth module.
    Affected if The system is a Bosch Infotainment ECU that incorporates Alps Alpine's Bluetooth stack.
  2. Retrieve the installed firmware version
    Access the ECU's diagnostic port or firmware information menu. Use the manufacturer's service tool or check the system info screen for the firmware version string associated with the Bluetooth/infotainment module.
    Affected if The firmware version cannot be confirmed as patched or falls within an affected version range not yet updated by the vendor.
  3. Verify Bluetooth functionality is enabled
    Check the infotainment system settings for Bluetooth activation status. Query the ECU's configuration or diagnostic interface to determine if the Bluetooth radio is powered on and discoverable.
    Affected if Bluetooth is currently enabled, as the vulnerability requires the L2CAP channel processing to be active to receive malicious packets.
  4. Confirm L2CAP protocol support
    Inspect the Bluetooth stack configuration or protocol logs to verify that L2CAP (Logical Link Control and Adaptation Protocol) channel establishment is permitted. This may be visible in the Bluetooth module's diagnostic or network trace data.
    Affected if L2CAP is available and not explicitly disabled at the protocol stack level, as the buffer overflow occurs during L2CAP channel processing.
  5. Assess network exposure of the ECU
    Review network segmentation and access controls surrounding the infotainment ECU. Check whether the Bluetooth interface is reachable from untrusted external devices or only from paired/authorized devices.
    Affected if The ECU's Bluetooth interface is exposed to external attackers, enabling remote exploitation via crafted L2CAP packets.

A user is affected if their Bosch Infotainment ECU runs an unpatched firmware version with Alps Alpine Bluetooth stack, has Bluetooth enabled with L2CAP support, and the ECU is network-accessible to untrusted Bluetooth devices.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Vendor-supplied firmware update for the Infotainment ECU is required. Until patch availability, disable Bluetooth functionality on affected vehicles and limit ECU network exposure.

Have this fixed Scoped from the published advisory
  • Consultation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
48.0 hours of engineering $8,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,184.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data