CVE-2025-21488
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 while decoding this RTP packet headers received by UE from the network when the padding bit is set.
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 an information disclosure vulnerability in User Equipment (UE) that occurs when decoding RTP (Real-time Transport Protocol) packet headers. When the RTP packet's padding bit is set, improper handling of the padding during header decoding leads to information disclosure. This could expose sensitive data from memory or allow attackers to gather reconnaissance 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 or Wi-Fi moduleCheck the device hardware specifications, kernel modules, or system information to determine if the device uses any of the following: Fastconnect 6200, 6700, 6900, 7800, Msm8996au, Qca6564, Qca6564a, or Qca6564au.Affected if The device uses any of the listed Qualcomm chipsets or firmware modules.
-
Confirm RTP header decoding is activeCheck if the device or its software stack processes RTP (Real-time Transport Protocol) traffic. This may be visible in active network connections, process lists for media servers, or configuration files for VoIP/video applications.Affected if RTP packet processing is enabled and the device handles RTP streams.
-
Inspect RTP packet handling configurationReview any configuration settings, drivers, or firmware parameters related to RTP header parsing. Look for settings that control how padding bits in RTP headers are processed.Affected if RTP handling is enabled and the padding bit in RTP headers is being processed by the affected firmware.
-
Verify firmware version is from the affected product listQuery the installed firmware version for the Qualcomm component using vendor tools, /proc filesystem, or system information interfaces. All versions of Fastconnect 6200, 6700, 6900, 7800, Msm8996au, Qca6564, Qca6564a, and Qca6564au are affected.Affected if The device runs any version of the listed Qualcomm firmware components.
A device is affected if it uses any of the listed Qualcomm chipsets or firmware modules and processes RTP traffic with padding bits in the headers.
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 patches or firmware updates to affected UE devices. Until a patch is available, consider network-level filtering or monitoring of RTP traffic to detect exploitation attempts.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21488 — 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-21488 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