Memory disclosure via unchecked userspace length
Published Sep 9, 2024 · Updated Mar 14, 2025
Heap over-read in Samsung Exynos 980, 850, 1080, 1280, 1380, 1330, 1480, W920, and W930 allows local users to read heap memory. The slsi_rx_blockack_ind() function trusts a userspace-supplied length without checking it against the heap buffer before reading data. Exploitation requires local high privileges and no user interaction; the documented consequence is memory disclosure without integrity or availability impact.
Summary
What happened
Heap over-read in Samsung Exynos 980, 850, 1080, 1280, 1380, 1330, 1480, W920, and W930 allows local users to read heap memory. The slsi_rx_blockack_ind() function trusts a userspace-supplied length without checking it against the heap buffer before reading data. Exploitation requires local high privileges and no user interaction; the documented consequence is memory disclosure without integrity or availability impact.
The record
- CVE
- CVE-2024-27365
- Published
- Sep 9, 2024
- Updated
- Mar 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Sep 9, 2024CVE publishedPublication date reported by the CVE source.
- Mar 14, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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