Kernel memory corruption via out-of-bounds driver access
Published Apr 8, 2020 · Updated Aug 5, 2024
Out-of-bounds access in a kernel driver on Samsung Exynos mobile devices running Android 6.0 through 8.0 allows local users to read or write memory. The undisclosed driver performs out-of-bounds reads and writes, but Samsung has not identified the driver, entry point, or attacker-controlled input. Root access is required to reach the flaw, and successful corruption can enable arbitrary code execution with kernel privileges.
Summary
What happened
Out-of-bounds access in a kernel driver on Samsung Exynos mobile devices running Android 6.0 through 8.0 allows local users to read or write memory. The undisclosed driver performs out-of-bounds reads and writes, but Samsung has not identified the driver, entry point, or attacker-controlled input. Root access is required to reach the flaw, and successful corruption can enable arbitrary code execution with kernel privileges.
The record
- CVE
- CVE-2018-21072
- Published
- Apr 8, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, CWE-125
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
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.
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