Kernel memory corruption via laf_read use-after-free
Published Feb 4, 2021 · Updated Aug 3, 2024
Use-after-free in LG mobile devices with Android 8.0, 8.1, 9.0, and 10 allows attackers to corrupt kernel memory through the USB laf gadget. The laf_read function in f_laf.c accesses memory after its object has been freed; public sources do not disclose the triggering state sequence. A USB host must interact with the gadget; published evidence establishes memory corruption but does not demonstrate code execution for this laf flaw.
Summary
What happened
Use-after-free in LG mobile devices with Android 8.0, 8.1, 9.0, and 10 allows attackers to corrupt kernel memory through the USB laf gadget. The laf_read function in f_laf.c accesses memory after its object has been freed; public sources do not disclose the triggering state sequence. A USB host must interact with the gadget; published evidence establishes memory corruption but does not demonstrate code execution for this laf flaw.
The record
- CVE
- CVE-2021-26689
- Published
- Feb 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416
- Attack vector
- Unavailable
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2021CVE 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?
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