Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Remote DoS in Unisoc NR Modem Input Validation

IdentifiersCVE-2025-11132CWE-20

CVE-2025-11132 is a vulnerability in the NR modem component caused by improper input validation. According to the provided content, malformed or unexpected input to the modem can trigger a system crash. The issue is described as remotely triggerable and does not require additional execution privileges, indicating that the vulnerable modem processing path can be reached without prior privilege escalation.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can cause a system crash, resulting in remote denial of service. Based on the provided information, the primary impact is loss of availability of the affected device or modem-related functionality, with no indication of code execution, privilege escalation, or data disclosure.

Mitigation

If you can’t patch tonight, do this now.

Until a vendor fix is applied, reduce exposure of the vulnerable modem interface where operationally possible by limiting attack surface to untrusted remote inputs and prioritizing rapid deployment of OEM/baseband firmware updates. In enterprise environments, prioritize devices receiving the December 2025 vendor-equivalent patch set and track lagging OEM integration for modem fixes. Specific compensating controls are not provided in the content.

Remediation

Patch, then assume compromise.

Apply the vendor/OEM security update that remediates CVE-2025-11132. The provided content places this issue among Unisoc modem vulnerabilities addressed in the December 2025 Android security update cycle, so affected devices should receive the relevant vendor firmware update and corresponding Android security patch level as made available by the device manufacturer.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
GoogleAndroidoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity2

Community discussion across Reddit, Mastodon, and other social sources.