Skip to main content
CVE-2025-47331VulnerabilityPublished

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

Affects Qualcomm SnapdragonSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.07% 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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Qualcomm, Inc.SnapdragonAffected
  • =AR8031
  • =AR8035
  • =CSR8811
  • =CSRA6620
  • =CSRA6640
  • =IPQ5010
  • =IPQ5028
  • =IPQ5300
  • =IPQ5302
  • =IPQ5312
  • =IPQ5332
  • =IPQ6000
  • =IPQ6010
  • =IPQ6018
  • =IPQ6028
  • =IPQ8076
  • =IPQ8078
  • =IPQ8173
  • =IPQ8174
  • =IPQ9008
  • =IPQ9048
  • =IPQ9554
  • =IPQ9570
  • =IPQ9574
  • =MDM9628
  • =QCA0000
  • =QCA2066
  • =QCA4024
  • =QCA6391
  • =QCA6574
  • =QCA6595
  • =QCA6696
  • =QCA8072
  • =QCA8075
  • =QCA8081
  • =QCA8082
  • =QCA8084
  • =QCA8085
  • =QCA8337
  • =QCA8386
  • =QCA9367
  • =QCA9377
  • =QCA9888
  • =QCA9889
  • =QCC710
  • =QCF8000
  • =QCF8001
  • =QCM2290
  • =QCM4490
  • =QCM5430
  • =QCM6125
  • =QCM6490
  • =QCM8550
  • =QCN5022
  • =QCN5024
  • =QCN5052
  • =QCN5054
  • =QCN5122
  • =QCN5124
  • =QCN5152
  • =QCN5154
  • =QCN5164
  • =QCN6023
  • =QCN6024
  • =QCN6100
  • =QCN6102
  • =QCN6112
  • =QCN6122
  • =QCN6132
  • =QCN6224
  • =QCN6274
  • =QCN6402
  • =QCN6412
  • =QCN6422
  • =QCN6432
  • =QCN9000
  • =QCN9001
  • =QCN9002
  • =QCN9003
  • =QCN9011
  • =QCN9012
  • =QCN9022
  • =QCN9024
  • =QCN9070
  • =QCN9072
  • =QCN9074
  • =QCN9100
  • =QCN9160
  • =QCN9274
  • =QCS2290
  • =QCS410
  • =QCS4490
  • =QCS5430
  • =QCS610
  • =QCS6125
  • =QCS6490
  • =QCS7230
  • =QCS8250
  • =QCS8550
  • =QCS9100
  • =QDU1010
  • =QDX1010
  • =QDX1011
  • =QEP8111
  • =QFW7114
  • =QFW7124
  • =QMP1000
  • =QXM8083
  • =SD660
  • =SDX55
  • =SDX61
  • =SG8275
  • =SM4635
  • =SM6475
  • =SM6650
  • =SM7435
  • =SM7550
  • =SM7635
  • =SM7675
  • =SM8635
  • =SM8735
  • =SM8750
  • =SW5100
  • =WCD9326
  • =WCD9335
  • =WCD9340
  • =WCD9341
  • =WCD9370
  • =WCD9371
  • =WCD9375
  • =WCD9378
  • =WCD9380
  • =WCD9385
  • =WCD9390
  • =WCD9395
  • =WCN3615
  • =WCN3910
  • =WCN3950
  • =WCN3980
  • =WCN3988
  • =WCN3990
  • =WCN6650
  • =WCN6740
  • =WCN6755
  • =WCN7750
  • =WCN7860
  • =WCN7861
  • =WCN7880
  • =WCN7881
  • =WSA8810
  • =WSA8815
  • =WSA8830
  • =WSA8832
  • =WSA8835
  • =WSA8840
  • =WSA8845
Fixed in–

AI-suggested

1. Monitor Qualcomm and device vendor advisories closely for firmware updates addressing CVE-2025-47331 and apply patches promptly. 2. Implement strict local access controls on devices using affected Snapdragon platforms to prevent unauthorized users from gaining low privilege access. 3. Employ endpoint detection and response (EDR) solutions to detect suspicious local activity that could indicate exploitation attempts. 4. For automotive and IoT deployments, enforce network segmentation and device authentication to limit attacker movement and access. 5. Conduct regular firmware inventory and vulnerability assessments to identify devices with vulnerable Qualcomm components. 6. Collaborate with device manufacturers to understand patch availability timelines and plan device update rollouts accordingly. 7. Educate users and administrators on the risks of local access vulnerabilities and enforce strong physical security controls. 8. Where feasible, consider deploying devices with alternative chipsets or architectures not affected by this vulnerability in high-risk environments.

Description

Information disclosure while processing a firmware event.

References

Community reviews

Loading reviews…