Cross-process data access via missing TLB flush
Published Mar 3, 2022 · Updated Aug 3, 2024
Memory corruption in Linux Kernel 3.6 through 5.15.5 allows local users to read or alter huge-page data from other processes. The hugetlb unmapping path clears a shared PUD without flushing the corresponding TLB entries, leaving stale translations to pages reallocated to another process. Exploitation requires local code execution, PUD-aligned shared huge-page mappings, available huge pages, and timely page reuse.
Summary
What happened
Memory corruption in Linux Kernel 3.6 through 5.15.5 allows local users to read or alter huge-page data from other processes. The hugetlb unmapping path clears a shared PUD without flushing the corresponding TLB entries, leaving stale translations to pages reallocated to another process. Exploitation requires local code execution, PUD-aligned shared huge-page mappings, available huge pages, and timely page reuse.
The record
- CVE
- CVE-2021-4002
- Published
- Mar 3, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-401, CWE-459
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 3, 2022CVE 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=affects kernel v3.6 and later through v5.15.5.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- hugetlbfs stale-TLB proof of conceptproof of concept · demonstrated
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