CVE-2025-47393

Kernel memory corruption via invalid resource array index

Published Jan 6, 2026 · Updated Jan 6, 2026

Memory corruption in Snapdragon Auto kernel drivers allows local users to corrupt memory through driver-managed resource access. The driver fails to validate an array index before using it to select a resource, producing an out-of-bounds access; Qualcomm has not disclosed the driver or code path. Successful exploitation requires local low-privilege access and compromises confidentiality, integrity, and availability within the automotive Linux OS kernel.

CVSS severity7.8
High
EPSS probability0.08%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Memory corruption in Snapdragon Auto kernel drivers allows local users to corrupt memory through driver-managed resource access. The driver fails to validate an array index before using it to select a resource, producing an out-of-bounds access; Qualcomm has not disclosed the driver or code path. Successful exploitation requires local low-privilege access and compromises confidentiality, integrity, and availability within the automotive Linux OS kernel.

The record

CVE
CVE-2025-47393
Published
Jan 6, 2026
Updated
Jan 6, 2026
Vendor
Qualcomm
Product
Snapdragon
Classifications
CWE-129, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 6, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 6, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=QAM8255P
  2. Affected versionversion=QAM8650P
  3. Affected versionversion=QAM8775P
  4. Affected versionversion=QAMSRV1H
  5. Affected versionversion=QAMSRV1M
  6. Affected versionversion=QCA6595
  7. Affected versionversion=QCA6698AQ
  8. Affected versionversion=QCA6797AQ
  9. Affected versionversion=SA7255P
  10. Affected versionversion=SA7775P
  11. Affected versionversion=SA8255P
  12. Affected versionversion=SA8620P
  13. Affected versionversion=SA8650P
  14. Affected versionversion=SA8770P
  15. Affected versionversion=SA8775P
  16. Affected versionversion=SA9000P
  17. Affected versionversion=SRV1H
  18. Affected versionversion=SRV1M

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Qualcomm · Snapdragonversion=QAM8255P; version=QAM8650P; version=QAM8775P; version=QAMSRV1H; version=QAMSRV1M; version=QCA6595; version=QCA6698AQ; version=QCA6797AQ; version=SA7255P; version=SA7775P; version=SA8255P; version=SA8620P; version=SA8650P; version=SA8770P; version=SA8775P; version=SA9000P; version=SRV1H; version=SRV1M

Published CVSS scores

7.8Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-129Improper Validation of Array Index
T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo