Kernel heap disclosure via misreported SD-card reads
Published May 10, 2022 · Updated Aug 3, 2024
Information disclosure in the Linux kernel's SD/MMC block driver allows local users to read kernel heap data via an erroring SD card. On a command error with retries remaining, mmc_blk_read_single can pass a stale success status to blk_update_request, reporting a completed read even though the device returned no data. An SD card that induces CRC or command-rejection errors is required; no additional execution privileges or user interaction are needed.
Summary
What happened
Information disclosure in the Linux kernel's SD/MMC block driver allows local users to read kernel heap data via an erroring SD card. On a command error with retries remaining, mmc_blk_read_single can pass a stale success status to blk_update_request, reporting a completed read even though the device returned no data. An SD card that induces CRC or command-rejection errors is required; no additional execution privileges or user interaction are needed.
The record
- CVE
- CVE-2022-20008
- Published
- May 10, 2022
- Updated
- Aug 3, 2024
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-908, T1005
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 10, 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=Android kernel
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.
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