dbcve.org
Simplicity Software Development KitApplication · Silabs

CVE-2025-12131

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-05
Fix available
A fix is available. Upgrade to after 2025.6.2 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 truncated 802.15.4 packet can lead to an assert, resulting in a denial of service.

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 · moderate confidence

The vulnerability exists in IEEE 802.15.4 packet parsing logic where a truncated (incomplete) frame triggers an assertion failure, causing the device or application to crash and resulting in denial of service.

MitigationImplement graceful error handling for malformed packets instead of asserting; add proper input validation on packet length fields before processing 802.15.4 frames.

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
Simplicity Software Development KitApplication
Affected:<= 2025.6.2

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 installed Simplicity SDK version
    Locate the SDK installation directory or check project build files for the Simplicity SDK version identifier. Common locations include the SDK manifest file, build configuration, or release notes in the project
    Affected if The SDK version is 2025.6.2 or earlier (any version <= 2025.6.2)
  2. Confirm IEEE 802.15.4 stack is in use
    Review project configuration to determine if the 802.15.4 wireless stack (either Ember ZNet, Silicon Labs Thread, or Zigbee stack) is compiled and enabled in the firmware or application
    Affected if IEEE 802.15.4 stack is included in the build or runtime configuration
  3. Verify packet reception from untrusted sources
    Inspect the network configuration and packet handler code to determine if the device accepts 802.15.4 frames from external or untrusted radio sources without prior validation
    Affected if The device processes incoming 802.15.4 packets from devices not in a trusted pairing list or without input validation at the MAC layer
  4. Locate 802.15.4 frame parsing code
    Search the project source for the IEEE 802.15.4 parsing implementation, typically in files related to MAC layer, RF stack, or packet handlers. Look for functions that process frame length and payload fields
    Affected if The codebase contains 802.15.4 frame parsing logic without proper length validation before buffer access
  5. Check for assertion usage in packet handling
    Examine the 802.15.4 parsing code for assert() or similar statements that terminate execution on unexpected frame conditions, particularly around frame length or completeness checks
    Affected if Assertions exist in the frame parsing path that trigger on truncated or malformed 802.15.4 frames

A user is affected if they are running Simplicity SDK version 2025.6.2 or earlier AND their application uses the IEEE 802.15.4 stack to process incoming wireless frames from potentially untrusted sources.

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 a release after 2025.6.2
Interim mitigation

Implement graceful error handling for malformed packets instead of asserting; add proper input validation on packet length fields before processing 802.15.4 frames.

Recommended fix Moderate confidence

Simplicity Software SDK > 2025.6.2 (obtain exact version from community.silabs.com)

  1. 1. Visit the Silicon Labs community website (community.silabs.com) to check for the latest Simplicity Software Development Kit release notes
  2. 2. Download the Simplicity Software SDK version newer than 2025.6.2 that contains the fix for the truncated 802.15.4 packet assert vulnerability
  3. 3. Before upgrading, review the SDK release notes for any migration requirements or breaking changes
  4. 4. Upgrade the Simplicity Software SDK to the fixed version
  5. 5. Test 802.15.4 packet handling to verify the vulnerability is resolved
Caveat Review release notes for potential breaking changes in the newer SDK version

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

Fix this in Simplicity Software Development Kit Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12131 — 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-2025-12131 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