CVE-2025-69278
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 confidenceA high-severity denial of service vulnerability exists in 5G NR (New Radio) modem firmware due to improper input validation. An attacker with network adjacency to the modem can send specially crafted input that triggers a system crash, causing complete loss of modem functionality without requiring any authentication or elevated privileges.
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.
-
Verify Android OS versionGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADBAffected if The displayed version is 13.0, 14.0, 15.0, or 16.0
-
Identify modem firmware versionRun 'getprop | grep -i radio' or 'getprop gsm.version.baseband' via ADB to retrieve the baseband/modem firmware version; consult device manufacturer documentation for version format interpretationAffected if The modem firmware is the one associated with the affected Android versions and has not been patched by the vendor
-
Confirm 5G NR capability is enabledGo to Settings > Network & Internet > Mobile Network > Preferred Network Type, or check if the device shows 5G/NR connection capability; run 'settings get global preferred_network_mode' via ADBAffected if 5G NR or LTE/5G auto mode is selected, enabling the vulnerable modem component
-
Check network exposure of modem interfaceReview firewall rules via 'iptables -L' or 'ip6tables -L' and verify mobile network segmentation; assess whether the device operates on carrier networks with adjacent attacker accessAffected if The device is directly accessible on mobile networks without network-level filtering between the modem and potential adjacent attackers
A device is affected if it runs Android 13.0-16.0 with an unpatched 5G NR modem firmware and has 5G capability enabled, exposing the modem to adjacent network attackers.
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 for the affected NR modem component. Implement robust input validation and bounds checking on all external inputs reaching the modem processing path. If patches are unavailable, consider network segmentation to limit modem exposure to untrusted attackers.
- Consultation8.0 h
- Implementation24.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69278 — 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-69278 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