CVE-2023-21642

Memory corruption via overprivileged physical-address access

Published May 2, 2023 · Updated Aug 2, 2024

Memory corruption in Qualcomm Snapdragon Auto HAB memory management allows local users to compromise data and interrupt affected platforms. HAB memory management grants overly broad system privileges when handling a physical address; Qualcomm has not disclosed the specific code path or invalid operation. Local access to an affected chipset is required, and successful exploitation can read or alter protected memory or crash the platform.

CVSS severity8.4
High
EPSS probability0.10%
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 Qualcomm Snapdragon Auto HAB memory management allows local users to compromise data and interrupt affected platforms. HAB memory management grants overly broad system privileges when handling a physical address; Qualcomm has not disclosed the specific code path or invalid operation. Local access to an affected chipset is required, and successful exploitation can read or alter protected memory or crash the platform.

The record

CVE
CVE-2023-21642
Published
May 2, 2023
Updated
Aug 2, 2024
Vendor
Qualcomm
Product
SA8155P Firmware
Classifications
CWE-284, T0890
Attack vector
local
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 2, 2023CVE publishedPublication date reported by the CVE source.
  2. Aug 2, 2024Record 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=0 <=*

What conditions does exploitation require?

Attack vectorlocal
Required privilegesunauthenticated

What is affected?

Qualcomm · SA8155P Firmwareversion=0 <=*
Qualcomm · SA9000P Firmwareversion=0 <=*
Qualcomm · SA8540P Firmwareversion=0 <=*
Qualcomm · SA6150P Firmwareversion=0 <=*
Qualcomm · SA8195P Firmwareversion=0 <=*
Qualcomm · Snapdragonversion=QAM8295P; version=QCA6574AU; version=QCA6696; version=SA6145P; version=SA6150P; version=SA6155P; version=SA8145P; version=SA8150P; version=SA8155P; version=SA8195P; version=SA8295P; version=SA8540P; version=SA9000P
Qualcomm · SA6155P Firmwareversion=0 <=*
Qualcomm · SA8295P Firmwareversion=0 <=*
Qualcomm · SA8145P Firmwareversion=0 <=*
Qualcomm · SA8150P Firmwareversion=0 <=*
Qualcomm · QAM8295P Firmwareversion=0 <=*
Qualcomm · QCA6574AU Firmwareversion=0 <=*
Qualcomm · SA6145P Firmwareversion=0 <=*
Qualcomm · QCA6696 Firmwareversion=0 <=*

Published CVSS scores

8.4Qualcomm, Inc.CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
7.8NIST NVDCVSS: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
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-284Improper Access Control
T0890Exploitation 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