System crash or code execution via context race
Published Jan 14, 2020 · Updated Aug 4, 2024
A use-after-free in affected Linux kernel i915 releases allows local users to crash the system or execute arbitrary code. i915_gem_context_destroy_ioctl looked up a GEM context before locking and removing its identifier, so concurrent destroy requests could both close the same context. Exposure requires an Intel GPU and local low-privileged access; affected ranges are 4.14 through 4.14.165, 4.19 through 4.19.96, and 5.x before 5.2.
Summary
What happened
A use-after-free in affected Linux kernel i915 releases allows local users to crash the system or execute arbitrary code. i915_gem_context_destroy_ioctl looked up a GEM context before locking and removing its identifier, so concurrent destroy requests could both close the same context. Exposure requires an Intel GPU and local low-privileged access; affected ranges are 4.14 through 4.14.165, 4.19 through 4.19.96, and 5.x before 5.2.
The record
- CVE
- CVE-2020-7053
- Published
- Jan 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 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.
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