dbcve.org
CWE-240Weakness · CWE-240

CVE-2025-4321

HIGH · 7.1 CVSS v4.0 Published 2025-11-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
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
In a Bluetooth device, using RS9116-WiseConnect SDK experiences a Denial of Service, if it receives malformed L2CAP packets, only hard reset will bring the device to normal operation

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

A denial of service vulnerability exists in Bluetooth devices using the RS9116-WiseConnect SDK. When the device receives malformed L2CAP (Logical Link Control and Adaptation Protocol) packets, it becomes completely unresponsive, and only a hard reset can restore normal operation.

MitigationApply any vendor-supplied firmware/security updates for the RS9116-WiseConnect SDK when available; until then, restrict Bluetooth device pairing and communication to trusted entities to reduce exposure to malicious L2CAP packets.

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

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 RS9116-WiseConnect SDK usage
    Examine your device documentation, firmware metadata, or system information to confirm the Bluetooth implementation uses the RS9116 chipset and WiseConnect SDK. Check for silkscreen markings on the module or bootloader/firmware strings that reference 'RS9116' or 'WiseConnect'.
    Affected if The device does not use RS9116-WiseConnect SDK, then this CVE does not apply.
  2. Locate firmware version information
    Access the device firmware version through manufacturer diagnostic tools, UART debug output, AT command interface, or firmware file metadata. Look for version strings in the firmware image or release notes provided by the vendor.
    Affected if No firmware version can be determined; compare any available version to vendor release notes to assess if updates addressing this issue have been applied.
  3. Verify Bluetooth is enabled
    Check the device configuration or runtime status to confirm Bluetooth functionality is active. This may involve querying the device state via API, checking configuration files, or observing LED indicators if documented.
    Affected if Bluetooth is disabled and cannot receive L2CAP packets, the vulnerability cannot be triggered.
  4. Confirm L2CAP channel availability
    Inspect device Bluetooth settings, profile configurations, or connection acceptance settings to determine if the device accepts incoming L2CAP connections or Classic Bluetooth connections. This may be visible in pairing settings, SDP records, or connection permission configs.
    Affected if The device blocks all incoming Bluetooth connections and L2CAP channels, reducing exposure to malformed packets.

A device is affected if it uses the RS9116-WiseConnect SDK with Bluetooth enabled and accessible, and the firmware has not been updated to address malformed L2CAP packet handling.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply any vendor-supplied firmware/security updates for the RS9116-WiseConnect SDK when available; until then, restrict Bluetooth device pairing and communication to trusted entities to reduce exposure to malicious L2CAP packets.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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