Skip to main content
VulnerabilityPublished Updated

CVE-2024-7139: silabs.com RS9116 Bluetooth SDK · Out-of-bounds Write

Affects silabs.com RS9116 Bluetooth SDKSource CVE Database V5

0

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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 19 Dec 2024

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
silabs.com RS9116 Bluetooth SDKAffected
  • =0
Fixed in–

AI-suggested

To mitigate CVE-2024-7139, European organizations should: 1) Verify if their devices use the affected RS9116 Bluetooth SDK version and plan for firmware updates as soon as patches become available from Silicon Labs. 2) Enable and configure watchdog timers on all embedded devices using this SDK to ensure automatic recovery from assertion failures without requiring manual resets. 3) Implement network segmentation and Bluetooth access controls to limit exposure to untrusted or unknown Bluetooth devices, reducing the attack surface. 4) Monitor Bluetooth traffic for anomalous L2CAP packets that could indicate exploitation attempts. 5) Engage with device vendors to confirm patch availability and deployment timelines. 6) Incorporate this vulnerability into incident response plans, ensuring rapid detection and recovery procedures are in place. 7) For critical environments, consider temporary disabling of Bluetooth interfaces if feasible until patches are applied. These steps go beyond generic advice by focusing on specific SDK usage, watchdog timer configuration, and operational controls tailored to embedded Bluetooth devices.

Description

Due to an unchecked buffer length, a specially crafted L2CAP packet can cause a buffer overflow. This buffer overflow triggers an assert, which results in a temporary denial of service.  If a watchdog timer is not enabled, a hard reset is required to recover the device.

References

Community reviews

Loading reviews…