Skip to main content
VulnerabilityPublished Updated

CVE-2024-7137: 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

  1. Monitor silabs.com and official channels for patches or firmware updates addressing CVE-2024-7137 and apply them promptly once available.
  2. Implement network segmentation and access controls to limit Bluetooth connectivity exposure, especially in sensitive environments.
  3. Employ Bluetooth device whitelisting and authentication mechanisms to restrict connections to trusted devices only.
  4. Conduct regular device inventory and firmware version audits to identify affected RS9116 SDK deployments.
  5. Where feasible, disable or restrict Bluetooth functionality on devices that do not require it to reduce attack surface.
  6. For critical systems, consider deploying intrusion detection systems capable of monitoring anomalous Bluetooth traffic patterns indicative of oversized L2CAP packets.
  7. Train operational staff to recognize and respond to device crashes potentially caused by this vulnerability, including procedures for safe hard resets and incident reporting.
  8. Engage with Silabs support for guidance on interim mitigations or workarounds until official patches are released.

Description

The L2CAP receive data buffer for L2CAP packets is restricted to packet sizes smaller than the maximum supported packet size. Receiving a packet that exceeds the restricted buffer length may cause a crash. A hard reset is required to recover the crashed device.

References

Community reviews

Loading reviews…