Integer OverflowWeakness · CWE-190

CVE-2025-12035

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-15

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

70/100

Remediation priority · Elevated

No privileges Zero-click

Official description

NVD · unedited

An integer overflow condition exists in Bluetooth Host stack, within the bt_br_acl_recv routine a critical path for processing inbound BR/EDR L2CAP traffic.

Technical summary

dbcve analysis · moderate confidence

Integer overflow in bt_br_acl_recv routine in Bluetooth Host stack during BR/EDR L2CAP traffic processing. The vulnerability occurs in a critical path for inbound ACL data, potentially allowing heap or stack corruption leading to code execution or denial of service.

MitigationApply vendor-specific patches for the Bluetooth stack; until patches are available, consider disabling unused Bluetooth BR/EDR functionality or restricting pairing to trusted devices only.

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

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Verify Bluetooth is enabled and BR/EDR mode is active

Check system Bluetooth status - on Linux: 'hciconfig' or 'bluetoothctl show'; on Windows: check Bluetooth adapter status in Device Manager or run 'netsh bluetooth show'; on Android: check Bluetooth settings for Classic Bluetooth (not LE only)

Affected if Bluetooth is enabled and BR/EDR (Classic Bluetooth) mode is actively running - the vulnerability only affects BR/EDR L2CAP processing, not BLE
Identify the Bluetooth stack version

On Linux: check BlueZ version with 'bluetoothd --version' or 'dpkg -l | grep bluez'; on Windows: run 'msinfo32' or check driver version in Device Manager for Bluetooth radio; on Android: check About Phone > Android version > Bluetooth stack details if available

Affected if The installed Bluetooth stack version is within or older than the affected range (if vendor发布了范围) and matches the product using the bt_br_acl_recv routine
Confirm L2CAP is available over BR/EDR

Check for L2CAP protocol support on ACL connections - on Linux: use 'hcitool con' to list ACL connections, then attempt 'sdptool browse' or monitor with 'btmon' for L2CAP channel activity; on Windows: check Bluetooth configuration for L2CAP channel availability

Affected if L2CAP over BR/EDR is enabled and actively used - the vulnerability triggers during inbound ACL data processing for L2CAP traffic
Monitor for anomalous ACL data handling

Use Bluetooth monitoring tools (btmon on Linux, Wireshark with Bluetooth traces on Windows) to observe inbound ACL packets for BR/EDR connections - look for unexpected packet sizes or malformed L2CAP headers

Affected if Inbound ACL packets with L2CAP payload are being processed and unusual packet handling or crashes occur in the Bluetooth stack process
Check for Bluetooth stack crashes or memory corruption indicators

Review system logs - on Linux: 'journalctl -b | grep -i bluetooth' or /var/log/syslog; on Windows: Event Viewer under Application logs for Bluetooth failures; check for sudden Bluetooth service restarts or kernel panics related to bt_br_acl_recv

Affected if Bluetooth stack exhibits unexplained crashes, memory corruption, or service restarts during active BR/EDR L2CAP communication

Your environment is likely affected if Bluetooth is enabled with BR/EDR mode active, the Bluetooth stack version matches an unpatched release, and L2CAP traffic over BR/EDR is being processed - monitor for crashes or corruption in Bluetooth-related processes.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply vendor-specific patches for the Bluetooth stack; until patches are available, consider disabling unused Bluetooth BR/EDR functionality or restricting pairing to trusted devices only.

Have this fixed Scoped from the published advisory

Consultation3.0 h
Implementation2.0 h
Testing6.0 h
Review / QA3.0 h

14.0 hours of engineering $2,400

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

github.com
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2025-12035?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 6.5 Medium

Exploit likelihood EPSS, next 30 days 0.2%

Remediation

Need this fixed?

Have this fixed 14 hrs · Moderate

Typical engagement from $2,400

Get a fix See the full breakdown ↓

We specialise in CVE remediation. Send your environment and we’ll scope CVE-2025-12035 and return a fixed quote.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References