CVE-2025-43706
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 · uneditedAn issue was discovered in L2 in Samsung Mobile Processor, Wearable Processor, and Modem Exynos 980, 990, 850, 1080, 2400, 1580, 9110, W920, W930, Modem 5123, and Modem 5400. Incorrect handling of RRC packets leads to 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 confidenceA vulnerability in the L2 layer of Samsung's cellular processors and modems allows malformed RRC (Radio Resource Control) packets to cause a Denial of Service. The issue affects multiple Exynos chipsets used in mobile phones, wearables, and cellular modems. An attacker sending specifically crafted RRC messages can crash the modem subsystem, potentially rendering cellular connectivity unavailable.
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 dataall versionsall versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your device's chipset modelCheck your device specifications or system information to determine the exact Exynos processor or cellular modem chipset model (e.g., Exynos 1080, Exynos 1580, Exynos 980, Exynos 990, Exynos 9110, Exynos 850, Exynos 2400, or Exynos W930). On Android devices, this may appear under Settings > About Phone > Processor or under kernel logs. For wearables, check the device model specifications on Samsung's product pages.Affected if The device uses any of the following chipsets: Exynos 1080, 1580, 980, 990, 9110, 850, 2400, or W930.
-
Confirm the device is a Samsung product with cellular connectivityVerify that the device is a Samsung mobile phone, wearable, or cellular modem that relies on an affected Exynos chipset for its cellular (LTE/5G) functionality. This vulnerability affects the modem subsystem, so devices without cellular modems are not impacted.Affected if The device is a Samsung phone, wearable, or cellular modem using an Exynos-based cellular processor from the affected list.
-
Check the current firmware versionOn Samsung devices, go to Settings > Software Update > Firmware Version, or check the baseband version under Settings > About Phone > Software Information. For wearables, check via the Samsung Wearable app or device settings. Record the firmware/baseband version number.Affected if The installed firmware/baseband version predates any Samsung security patch that addresses CVE-2025-43706, or no patch has been released for your specific device model yet.
-
Monitor for modem crashes or sudden cellular lossCheck device logs (logcat on Android) for modem-related crashes, baseband errors, or sudden loss of cellular signal. Users may notice the device showing 'No Service' or being unable to make calls or use mobile data unexpectedly.Affected if The modem subsystem crashes repeatedly or shows baseband/modem-related errors in system logs, especially after receiving RRC messages on LTE or 5G networks.
-
Verify vendor patch availabilityCheck Samsung's security bulletins or your carrier's firmware update notifications to see if a firmware update addressing CVE-2025-43706 has been released for your specific device model. This may appear as a baseband/modem update in a monthly security patch.Affected if Samsung has not released a firmware update for your device model that includes the CVE-2025-43706 fix, or the device is no longer receiving security updates.
A user is affected if their Samsung device uses one of the affected Exynos chipsets (1080, 1580, 980, 990, 9110, 850, 2400, or W930) and the vendor has not yet released a patched firmware version for their specific device model.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor-supplied firmware updates from Samsung for affected devices. Until patches are available, monitor network traffic for anomalous RRC messages and consider network-level filtering of suspicious packet patterns.
- Consultation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-43706 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-43706 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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