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

CVE-2025-32062

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

A stack-based buffer overflow vulnerability exists in the Alps Alpine Bluetooth stack within Bosch's Infotainment ECU. The flaw results from improper boundary validation of user-supplied data when processing specific packets on an established upper layer L2CAP channel. An attacker with Bluetooth adjacency can exploit this to execute arbitrary code with root privileges.

MitigationApply vendor-supplied patches for the Infotainment ECU Bluetooth stack; if no patch available, implement proper boundary validation checks on L2CAP channel data before copying to stack buffers, and consider network segmentation of the infotainment system.

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 Infotainment system
    Determine if the target system is a Bosch Infotainment ECU. Check system documentation, model numbers, or hardware identifiers. On Linux systems, examine /proc/cpuinfo, dmesg, or boot logs for 'Bosch' or 'Infotainment' references.
    Affected if The system is a Bosch Infotainment ECU using the Alps Alpine Bluetooth stack.
  2. Confirm Alps Alpine Bluetooth stack presence
    Identify the Bluetooth stack in use. On Linux, run 'hciconfig -a' or check 'bluetoothctl info'. Examine loaded modules or installed packages for 'alps' or 'alps_alpine' references. Check Bluetooth firmware or driver files in /lib/firmware or /etc/bluetooth/.
    Affected if The system uses the Alps Alpine Bluetooth stack in a Bosch Infotainment ECU.
  3. Verify Bluetooth is enabled
    Run 'hciconfig' or 'bluetoothctl show' to check if Bluetooth adapters are powered on. Check 'rfkill list' for Bluetooth status. On embedded systems, inspect /sys/class/bluetooth/ for active adapters.
    Affected if Bluetooth is enabled and an adapter is active, creating a reachable attack surface.
  4. Check for active L2CAP connections
    Monitor for L2CAP channels using 'btmon' or 'hcidump'. On Linux, use 'sdptool browse' to enumerate L2CAP services. Check /proc/bluetooth/ or bluetoothctl 'info' output for connected L2CAP channels.
    Affected if Upper layer L2CAP channels are established, which is required for the vulnerable code path to be triggered.
  5. Check Bluetooth stack version
    Query the Bluetooth stack version if available. On Linux, try 'hciconfig -a' for version info, check firmware version via 'btmgmt -i hci0 info', or examine kernel logs with 'dmesg | grep -i bluetooth'. Compare against any vendor-released version information.
    Affected if The installed Alps Alpine Bluetooth stack version does not include the boundary validation fix for L2CAP channel data.

You are affected if your system is a Bosch Infotainment ECU running the Alps Alpine Bluetooth stack with Bluetooth enabled and active L2CAP channels, and the installed version lacks the boundary validation fix for L2CAP packet processing.

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

Apply vendor-supplied patches for the Infotainment ECU Bluetooth stack; if no patch available, implement proper boundary validation checks on L2CAP channel data before copying to stack buffers, and consider network segmentation of the infotainment system.

Have this fixed Scoped from the published advisory
  • Consultation12.0 h
  • Implementation16.0 h
  • Testing20.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32062 — 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-32062 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