Kernel-memory disclosure via uninitialized SWIOTLB buffers
Published Mar 23, 2022 · Updated Aug 2, 2024
Information disclosure in Linux Kernel 5.17-rc8 allows local users to read kernel memory through SWIOTLB DMA_FROM_DEVICE mappings. During mapping, swiotlb fails to initialize a DMA_FROM_DEVICE bounce buffer from the original buffer, so later CPU synchronization copies stale contents into caller-visible memory. Exploitation requires local low-privileged code to reach a device path that uses SWIOTLB, and the bounded impact is disclosure of unrelated kernel data.
Summary
What happened
Information disclosure in Linux Kernel 5.17-rc8 allows local users to read kernel memory through SWIOTLB DMA_FROM_DEVICE mappings. During mapping, swiotlb fails to initialize a DMA_FROM_DEVICE bounce buffer from the original buffer, so later CPU synchronization copies stale contents into caller-visible memory. Exploitation requires local low-privileged code to reach a device path that uses SWIOTLB, and the bounded impact is disclosure of unrelated kernel data.
The record
- CVE
- CVE-2022-0854
- Published
- Mar 23, 2022
- Updated
- Aug 2, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-200, CWE-401, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 23, 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=Linux kernel 5.17-rc8
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