Skip to main content
CVE-2025-12035VulnerabilityPublished Updated

CVE-2025-12035: zephyrproject-rtos Zephyr · Integer Overflow or Wraparound

Affects zephyrproject-rtos ZephyrSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.3.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.3.0
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade zephyrproject-rtos Zephyr to 4.3.0.

Affected software

ProductAffectedFixed in
zephyrproject-rtosZephyrAffected
  • <4.3.0
Fixed in
  • 4.3.0
GitHubzephyrproject-rtos/zephyrpkg:github/zephyrproject-rtos/zephyrOther threatsAffected
  • *
Fixed in–
GitHubZephyrpkg:github/ZephyrOther threatsAffected
  • <4.3.0
Fixed in
  • 4.3.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Zephyr project communications and apply official patches promptly once released to address CVE-2025-12035. 2. Implement strict input validation and boundary checks in the Bluetooth stack to prevent integer overflow conditions. 3. Employ Bluetooth traffic filtering and segmentation to limit exposure to untrusted devices, especially in industrial and automotive environments. 4. Disable BR/EDR Bluetooth functionality on devices where it is not required to reduce attack surface. 5. Conduct thorough testing and fuzzing of Bluetooth input handling routines to detect similar vulnerabilities proactively. 6. Use network segmentation and access controls to isolate vulnerable embedded devices from critical infrastructure. 7. Maintain up-to-date asset inventories to identify all Zephyr-based devices and prioritize remediation efforts. 8. Educate operational technology (OT) and embedded system teams about the risks of Bluetooth vulnerabilities and best practices for secure configuration.

Description

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.

References

Community reviews

Loading reviews…