CVE-2025-47371
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 · uneditedTransient DOS when an LTE RLC packet with invalid TB is received by UE.
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 is a denial-of-service vulnerability in LTE (Long Term Evolution) User Equipment (UE) where receiving an RLC (Radio Link Control) packet containing an invalid Transport Block (TB) causes a transient service disruption. The vulnerability stems from improper input validation when processing malformed RLC packets at the radio interface layer.
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/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 Qualcomm chipset or platform in your deviceCheck your device documentation, system information, or AT command interface (e.g., ATI, AT+GMR) to determine the Qualcomm chipset model such as Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6800/6900, or a 5G Fixed Wireless Access platformAffected if The device uses any of the listed Qualcomm chipsets (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6800/6900, or 5G Fixed Wireless Access)
-
Determine the firmware version of the Qualcomm componentQuery the firmware version through device-specific interfaces such as AT commands (e.g., AT+QVERSION, AT+GMR), manufacturer diagnostic tools, or the device's firmware information page. Record the exact firmware version stringAffected if The installed firmware version matches any of the affected Qualcomm firmware versions listed for your platform
-
Verify LTE connectivity is activeCheck if the device has an active LTE connection by observing network status indicators, using AT commands (e.g., AT+CEREG?, AT+CREG?), or checking the modem connection state. The RLC layer vulnerability is triggered only when LTE is operationalAffected if The device maintains an active LTE connection and is capable of receiving RLC packets
-
Confirm the device processes RLC packets at the radio interfaceThis is inherent to LTE operation - no configuration check needed. The RLC (Radio Link Control) layer is always active when LTE is enabled. You can verify by confirming the device operates in LTE mode (check with AT+CNMP? or similar network mode commands)Affected if The device operates in LTE mode, meaning the vulnerable RLC input validation code path is present and potentially reachable
You are affected if your device uses any of the listed Qualcomm platforms (Ar8035, Csra6620, Csra6640, Fastconnect 6200/6700/6800/6900, or 5G Fixed Wireless Access) with LTE connectivity, as the vulnerable RLC packet validation code is present in all firmware versions of these platforms.
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-specific firmware/software updates for affected UE devices (including modems, IoT devices, and mobile handsets). Network operators may implement radio access network filtering to detect and drop malformed RLC packets before they reach UE devices.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47371 — 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-47371 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