Privilege escalation via missing GPU TLB flush
Published Mar 25, 2022 · Updated Aug 2, 2024
Random memory access in the Linux kernel i915 driver 5.17-rc2 allows local users to disclose or corrupt memory by submitting GPU code. The driver releases GPU-buffer backing pages without first flushing stale TLB entries, so undeclared GPU accesses can continue after those pages are reassigned. Access requires a Gen8 or newer Intel GPU; without an active IOMMU, consequences include data disclosure, memory corruption, a system crash, or privilege escalation.
Summary
What happened
Random memory access in the Linux kernel i915 driver 5.17-rc2 allows local users to disclose or corrupt memory by submitting GPU code. The driver releases GPU-buffer backing pages without first flushing stale TLB entries, so undeclared GPU accesses can continue after those pages are reassigned. Access requires a Gen8 or newer Intel GPU; without an active IOMMU, consequences include data disclosure, memory corruption, a system crash, or privilege escalation.
The record
- CVE
- CVE-2022-0330
- Published
- Mar 25, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-281, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2022CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=kernel 5.17-rc2
What conditions does exploitation require?
What is affected?
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