Kernel memory corruption via tsmux heap write
Published Mar 24, 2020 · Updated Aug 4, 2024
Out-of-bounds write in Samsung mobile devices O(8.x), P(9.0), and Q(10.0) software allows local users to corrupt kernel memory via the tsmux driver. The tsmux driver performs a heap write outside its allocated buffer; public records do not disclose the triggering operation or input. Local low-privilege access is required, and the record does not document whether exploitation yields code execution or service interruption.
Summary
What happened
Out-of-bounds write in Samsung mobile devices O(8.x), P(9.0), and Q(10.0) software allows local users to corrupt kernel memory via the tsmux driver. The tsmux driver performs a heap write outside its allocated buffer; public records do not disclose the triggering operation or input. Local low-privilege access is required, and the record does not document whether exploitation yields code execution or service interruption.
The record
- CVE
- CVE-2020-10842
- Published
- Mar 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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.
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