dbcve.org
Gecko Software Development KitApplication · Silabs

CVE-2024-0240

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-15
Fix available
A fix is available. Upgrade to 4.3.0 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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.

NVD · unedited
A memory leak in the Silicon Labs' Bluetooth stack for EFR32 products may cause memory to be exhausted when sending notifications to multiple clients, this results in all Bluetooth operations, such as advertising and scanning, to stop.

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.

dbcve analysis · high confidence

Memory leak in Silicon Labs' Bluetooth stack for EFR32 products. When sending notifications to multiple BLE clients, memory is allocated but not properly freed, causing progressive memory exhaustion that eventually halts all Bluetooth operations including advertising and scanning.

MitigationAwait firmware patch from Silicon Labs addressing the memory leak in the Bluetooth stack. In the interim, limit the number of connected notification clients and monitor memory usage on affected devices.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Gecko Software Development KitApplication
Affected:< 4.3.0

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.

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? 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.

dbcve checks

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

  1. Identify the Gecko SDK version in your firmware build
    Review your build artifacts, manifest files, or firmware release notes to find the Silabs Gecko SDK version used (for example, check the sdk_version or gecko_sdk_version variable in your build configuration)
    Affected if The installed SDK version is any version prior to 4.3.0 (for example, 4.2.x, 4.1.x, or earlier)
  2. Confirm the device implements BLE notification operations
    Inspect your application code or BLE stack configuration for any gatt_server_send_notification or similar BLE notification API calls that push data to connected BLE clients
    Affected if Your firmware code sends BLE notifications to one or more connected clients using the Silicon Labs Bluetooth stack
  3. Check for memory monitoring capability
    Examine whether your firmware includes memory usage tracking, heap monitoring, or diagnostic functions that report available RAM (for example, call stack size, heap remaining, or custom memory watchdog)
    Affected if You cannot observe heap or RAM consumption on the device (making progressive memory exhaustion difficult to detect)
  4. Look for Bluetooth operation failures
    Monitor device logs, status outputs, or diagnostic interfaces for signs that advertising stops, scanning halts, or connection failures occur after extended operation with multiple notification clients
    Affected if The device exhibits progressive failure of BLE functions (advertising stops, scanning halts, connections drop) after serving notifications to multiple BLE clients over time

You are affected if your firmware uses a Gecko SDK version below 4.3.0 AND implements BLE notification functionality to multiple clients, as the memory leak will eventually exhaust available memory and halt all Bluetooth operations.

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.3.0 or later
Fixed in 4.3.0
Interim mitigation

Await firmware patch from Silicon Labs addressing the memory leak in the Bluetooth stack. In the interim, limit the number of connected notification clients and monitor memory usage on affected devices.

Recommended fix High confidence

Gecko SDK 4.3.0

  1. Download the Gecko Software Development Kit version 4.3.0 or later from the official Silicon Labs website or repository
  2. Ensure all development environments and build tools are closed before upgrading
  3. Back up existing projects and configurations that rely on the current SDK installation
  4. Install or extract the new Gecko SDK version 4.3.0 to replace the existing installation
  5. Update any project files, makefiles, or build configurations to reference the new SDK path if necessary
  6. Rebuild all projects that use the Bluetooth stack to link against the updated libraries
  7. Test that Bluetooth operations (advertising, scanning, notifications) function correctly after the upgrade
Caveat Review release notes for 4.3.0 to check for API changes or behavioral differences in the Bluetooth stack that may require code modifications

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Gecko Software Development Kit Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-0240 — 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 Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

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

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