CVE-2024-7138: silabs.com RS9116 Bluetooth SDK · Reachable Assertion
Affects silabs.com RS9116 Bluetooth SDKSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| silabs.com RS9116 Bluetooth SDK | Affected
| Fixed in– |
AI-suggested
To mitigate CVE-2024-7138 effectively, organizations should: 1) Enable and verify the functionality of watchdog timers on all devices using the RS9116 Bluetooth SDK to ensure automatic recovery from assertion-triggered DoS states without requiring manual resets. 2) Monitor vendor communications closely for official patches or firmware updates addressing this vulnerability and apply them promptly once available. 3) Implement network-level controls to restrict Bluetooth communication to trusted devices only, reducing the risk of receiving malformed packets from unauthorized sources. 4) Conduct thorough testing of Bluetooth-enabled devices under malformed packet conditions to evaluate resilience and recovery mechanisms. 5) Where feasible, consider deploying intrusion detection systems capable of identifying anomalous Bluetooth traffic patterns indicative of exploitation attempts. 6) Maintain an inventory of all devices using the RS9116 SDK to prioritize patching and mitigation efforts. 7) Educate operational staff on recognizing symptoms of Bluetooth device DoS and procedures for safe device resets to minimize downtime.
Description
An assert may be triggered, causing a temporary denial of service when a peer device sends a specially crafted malformed L2CAP packet. If a watchdog timer is not enabled, a hard reset is required to recover the device.