CVE-2025-11131
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 · uneditedIn nr modem, there is a possible system crash due to improper input validation. This could lead to remote denial of service with no additional execution privileges needed
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 confidenceThis vulnerability in the 5G NR (New Radio) modem involves improper input validation that can be exploited remotely to cause a system crash, resulting in denial of service. The attack requires no additional execution privileges, suggesting the vulnerability is directly accessible via network-facing modem interfaces.
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= 13.0= 14.0= 15.0= 16.0CVSS 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 the operating systemCheck if the device runs Google Android OS. On the device, go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB.Affected if The device is not running Google Android OS, then it is not affected by this specific CVE.
-
Check the Android versionReview the installed Android version against the affected list. On the device: Settings > About Phone > Android version. Via ADB: 'adb shell getprop ro.build.version.release'Affected if The installed version is exactly 13.0, 14.0, 15.0, or 16.0, the device falls within the affected version range.
-
Verify 5G NR modem is presentCheck if the device has 5G NR modem hardware and the modem is enabled. On Android: Settings > Network & Internet > Mobile Network > Preferred Network Type, or check for 5G-related settings. Via ADB: 'adb shell settings get global preferred_network_mode'Affected if The device lacks 5G NR modem capability or the modem is disabled, the specific attack surface for this CVE does not exist.
-
Assess network exposure of modem interfaceDetermine if the 5G NR modem interface is accessible from network-facing services. Review firewall rules: 'adb shell iptables -L' and check for exposed modem management ports. Verify if mobile network APIs or diagnostic interfaces are accessible.Affected if The modem interface is directly network-accessible without segmentation, the vulnerability is exploitable in the attack scenario described.
A device is affected if it runs Android 13.0, 14.0, 15.0, or 16.0 with an active 5G NR modem that has network-accessible interfaces.
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-provided patches or firmware updates for the NR modem component to address the input validation flaw. If no patch is available, consider network segmentation to limit exposure of the modem interface.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11131 — 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-11131 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