CVE-2025-21484
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 · uneditedInformation disclosure when UE receives the RTP packet from the network, while decoding and reassembling the fragments from RTP packet.
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 confidenceInformation disclosure vulnerability in User Equipment (UE) when receiving and decoding RTP packets from the network. During the reassembly of fragmented RTP packets, the decoder improperly handles data leading to exposure of sensitive information.
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
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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 model in your deviceCheck the device specifications, system information, or baseband firmware details to determine if the chipset is one of: Sm8750, Sm8750p, Sm8850, Sm8850p, Smart Audio 200 Platform, Smart Display 200 Platform, Snapdragon 208 Processor, or Snapdragon 210 ProcessorAffected if The device contains any of these listed Qualcomm chipsets or platforms
-
Check the baseband/firmware versionLocate the baseband or system firmware version information in the device settings, about page, or through engineering diagnostic tools. Compare against the affected product list where all versions are impactedAffected if The installed firmware version corresponds to any of the affected products listed (all versions are vulnerable)
-
Determine if RTP packet processing is enabledReview the device network configuration, VoIP settings, video calling applications, or streaming services to determine if the device is configured to receive or decode RTP (Real-time Transport Protocol) packets from the networkAffected if RTP packet reception and decoding is enabled and the device processes RTP traffic from the network
-
Verify if the device receives RTP traffic from untrusted sourcesInspect network traffic logs, firewall rules, or packet captures to determine if the device is accepting RTP connections from untrusted or external network sourcesAffected if The device processes RTP packets originating from untrusted or non-whitelisted network sources
Your device is affected if it contains any of the listed Qualcomm chipsets (Sm8750, Sm8850, Smart Audio/Display 200, Snapdragon 208/210) and has RTP packet reception and decoding enabled, particularly from untrusted network sources.
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 security updates to the UE baseband/firmware addressing RTP packet reassembly. Limit RTP traffic to trusted network sources to reduce exposure.
- Consultation8.0 h
- Implementation40.0 h
- Testing20.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 $21,184.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21484 — 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-21484 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