Heap overwrite via unchecked userspace RTT identifier
Published Sep 9, 2024 · Updated Mar 17, 2025
Out-of-bounds write in Samsung Exynos mobile processors allows local users to corrupt heap memory through a userspace RTT identifier. The slsi_rx_range_done_ind() function uses rtt_id from userspace without validating it before a heap write, allowing an out-of-range overwrite. Reaching the flaw requires local high-privilege access, and Samsung describes no demonstrated consequence beyond heap corruption.
Summary
What happened
Out-of-bounds write in Samsung Exynos mobile processors allows local users to corrupt heap memory through a userspace RTT identifier. The slsi_rx_range_done_ind() function uses rtt_id from userspace without validating it before a heap write, allowing an out-of-range overwrite. Reaching the flaw requires local high-privilege access, and Samsung describes no demonstrated consequence beyond heap corruption.
The record
- CVE
- CVE-2024-27387
- Published
- Sep 9, 2024
- Updated
- Mar 17, 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 17, 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