VulnerabilityPublished 24 Sep 2025Updated 25 Sep 2025

CVE-2025-27030: Qualcomm Snapdragon · Buffer Over-read

Affects Qualcomm SnapdragonSource CVE Database V5

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

6.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.08% chance of exploitation in 30 days – higher than 0% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:L

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Given the local access requirement, European organizations should focus on minimizing the risk of local exploitation by enforcing strict device access controls and application sandboxing. Specifically, organizations should: 1) Ensure all devices using affected Qualcomm Snapdragon chipsets run the latest firmware and operating system versions, applying vendor patches as soon as they become available. 2) Restrict installation of untrusted or unsigned applications that could attempt to invoke the vulnerable calibration data routines. 3) Employ mobile device management (MDM) solutions to enforce security policies, including application whitelisting and privilege restrictions. 4) Monitor device behavior for unusual local access attempts or privilege escalations that could indicate exploitation attempts. 5) For automotive and IoT deployments, isolate critical communication modules from general-purpose computing environments to reduce attack vectors. 6) Engage with Qualcomm and device manufacturers to obtain timely updates and security advisories. 7) Conduct security audits and penetration testing focused on local privilege escalation and information disclosure vectors to identify potential exploitation paths. These steps go beyond generic advice by emphasizing local access control, application vetting, and segmentation tailored to the specific nature of this vulnerability.

Description

information disclosure while invoking calibration data from user space to update firmware size.

Impact

For European organizations, the impact of CVE-2025-27030 can be significant, especially those relying on devices and systems powered by affected Qualcomm Snapdragon chipsets. This includes enterprises using mobile devices, automotive manufacturers integrating Snapdragon-based telematics and communication modules, and IoT deployments in smart infrastructure. The information disclosure could lead to leakage of sensitive calibration or firmware data, which may assist attackers in crafting more sophisticated exploits or reverse engineering proprietary technology. In automotive contexts, this could undermine vehicle security or privacy, potentially affecting connected car services and safety features. For mobile users, the vulnerability could expose private data or cryptographic material stored or processed by the chipset firmware. Although exploitation requires local access with low privileges, the widespread deployment of these chipsets means that malware or malicious insiders could exploit this flaw to escalate information gathering capabilities. The absence of known exploits in the wild currently reduces immediate risk, but the broad attack surface and critical nature of affected devices warrant proactive mitigation to prevent future exploitation.

CWE-126Buffer Over-read (opens in a new tab)
Variant weakness
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.qualcomm.com/product/publicresources/securitybulletin/september-2025-bulletin.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 2 Oct 2025, 01:06 UTC

WeaknessesCWE-126

Technical details

References

Community reviews

Related threats