CVE-2025-21483
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 · uneditedMemory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs.
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 confidenceMemory corruption vulnerability in User Equipment (UE) occurring during the reassembly of NALUs (Network Abstraction Layer Units) from incoming RTP packets. The vulnerability allows remote attackers to trigger memory corruption via specially crafted RTP packets, likely leading to code execution.
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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 model in your device or equipmentCheck the device hardware specifications, system information, or baseband processor details to determine the exact Qualcomm model number (e.g., Apq8017, Apq8064au, Aqt1000, Fastconnect 6200/6700/6800/6900/7800)Affected if The device uses any of the listed affected Qualcomm chipset models
-
Confirm the firmware versionAccess the device's firmware/baseband information via AT commands (for mobile devices), system diagnostics, or vendor documentation to retrieve the installed firmware versionAffected if The firmware version matches one of the affected products listed (all versions for each model)
-
Verify RTP packet processing is enabledCheck if the device or baseband processor is configured to receive and process RTP (Real-time Transport Protocol) streams, particularly for video or multimedia transmissionAffected if RTP receive functionality is enabled on the device
-
Confirm NALU reassembly is activeInspect whether the device performs NALU (Network Abstraction Layer Unit) reassembly from incoming RTP packets, typically found in video streaming or VoIP implementationsAffected if The device performs NALU reassembly from RTP streams
Your environment is affected if you have devices using any of the listed Qualcomm chipsets (Apq8017, Apq8064au, Aqt1000, Fastconnect 6200/6700/6800/6900/7800) with firmware that processes RTP packets and performs NALU reassembly.
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 patches for affected UE devices/baseband processors; implement RTP packet validation and bounds checking at network edge if vendor updates unavailable.
- 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-21483 — 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-21483 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