How severe is CVE-2025-21427?

CVE-2025-21427 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability low.

Is CVE-2025-21427 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2025-21427?

CVE-2025-21427 primarily affects Qualcomm Sm6250 Firmware. In total, 179 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2025-21427?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2025-21427 have an EU (EUVD) identifier?

Yes. CVE-2025-21427 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20492.

When was CVE-2025-21427 published?

CVE-2025-21427 was published on 2025-07-08 and last updated on 2026-06-17.

CVE-2025-21427

CVE-2025-21427 is a high-severity vulnerability in Qualcomm Sm6250 Firmware with a CVSS 3.x base score of 8.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-125.

Key facts

Severity: High (CVSS 3.x base score 8.2)
EPSS exploit prediction: 0% (10th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-20492
Weakness: CWE-125
Affected product: Qualcomm Sm6250 Firmware
Published: 2025-07-08
Last modified: 2026-06-17

Description

Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network.

Frequently asked questions

What is CVE-2025-21427?: Information disclosure while decoding this RTP packet Payload when UE receives the RTP packet from the network.
How severe is CVE-2025-21427?: CVE-2025-21427 has a CVSS 3.x base score of 8.2, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability low.
Is CVE-2025-21427 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (10th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-21427?: CVE-2025-21427 primarily affects Qualcomm Sm6250 Firmware. In total, 179 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2025-21427?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2025-21427 have an EU (EUVD) identifier?: Yes. CVE-2025-21427 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-20492.
When was CVE-2025-21427 published?: CVE-2025-21427 was published on 2025-07-08 and last updated on 2026-06-17.

References

https://docs.qualcomm.com/product/publicresources/securitybulletin/july-2025-bulletin.html

Affected products (179)

cpe:2.3:o:qualcomm:sm6250_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sm6370_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sm7315_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sm7325p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:sm8550p_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:smart_display_200_platform_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_210_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_212_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_4_gen_1_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_4_gen_2_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_429_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_460_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_480_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_480\+_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_625_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_626_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_660_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_662_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_670_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_675_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_678_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_680_4g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_685_4g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_695_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_710_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_720g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_730_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_730g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_732g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_778g_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_778g\+_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_780g_5g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_782g_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_7c\+_gen_3_compute_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_8_gen_1_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_8_gen_2_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_8_gen_3_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_8\+_gen_1_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_8\+_gen_2_mobile_firmware:-:*:*:*:*:*:*:*
cpe:2.3:o:qualcomm:snapdragon_820_automotive_firmware:-:*:*:*:*:*:*:*

More vulnerabilities in Qualcomm Sm6250 Firmware

CVE-2025-21483 — Critical (CVSS 9.8): Memory corruption when the UE receives an RTP packet from the network, during the reassembly of NALUs.
CVE-2023-22388 — Critical (CVSS 9.8): Memory Corruption in Multi-mode Call Processor while processing bit mask API.
CVE-2023-28562 — Critical (CVSS 9.8): Memory corruption while handling payloads from remote ESL.
CVE-2022-40510 — Critical (CVSS 9.8): Memory corruption due to buffer copy without checking size of input in Audio while voice call with EVS vocoder.
CVE-2022-40514 — Critical (CVSS 9.8): Memory corruption due to buffer copy without checking the size of input in WLAN Firmware while processing CCKM IE in…
CVE-2022-22088 — Critical (CVSS 9.8): Memory corruption in Bluetooth HOST due to buffer overflow while parsing the command response received from remote

All CVEs affecting Qualcomm Sm6250 Firmware →

Other CWE-125 (Out-of-bounds Read) vulnerabilities

CVE-2026-24826 — Critical (CVSS 10.0): Out-of-bounds Write, Divide By Zero, NULL Pointer Dereference, Use of Uninitialized Resource, Out-of-bounds Read,…
CVE-2024-22004 — Critical (CVSS 10.0): Due to length check, an attacker with privilege access on a Linux Nonsecure operating system can trigger a…
CVE-2021-41556 — Critical (CVSS 10.0): sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that…
CVE-2021-21777 — Critical (CVSS 10.0): An information disclosure vulnerability exists in the Ethernet/IP UDP handler functionality of EIP Stack Group OpENer…
CVE-2017-14451 — Critical (CVSS 10.0): An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. A…
CVE-2013-0767 — Critical (CVSS 10.0): The nsSVGPathElement::GetPathLengthScale function in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and…

Browse all CWE-125 (Out-of-bounds Read) vulnerabilities →