Memory corruption via double-freed hyp-assign state
Published Jun 6, 2023 · Updated Aug 3, 2024
A double free in Qualcomm chipset Linux Networking firmware allows local users to corrupt memory while processing a hypervisor assignment. The TZ Firmware networking path frees allocation state twice while handling the hyp-assign operation, corrupting memory-management state. Local execution requires no privileges or user interaction; Qualcomm has not disclosed whether exploitation causes a crash or code execution.
Summary
What happened
A double free in Qualcomm chipset Linux Networking firmware allows local users to corrupt memory while processing a hypervisor assignment. The TZ Firmware networking path frees allocation state twice while handling the hyp-assign operation, corrupting memory-management state. Local execution requires no privileges or user interaction; Qualcomm has not disclosed whether exploitation causes a crash or code execution.
The record
- CVE
- CVE-2022-40522
- Published
- Jun 6, 2023
- Updated
- Aug 3, 2024
- Vendor
- Qualcomm
- Product
- SA8155P Firmware
- Classifications
- CWE-415
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2023CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.
- Affected versionversion=0 <=*
What conditions does exploitation require?
What is affected?
Published CVSS scores
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.
Weakness, pattern, technique
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