Kernel-memory disclosure via uninitialized ioctl output
Published Jul 12, 2023 · Updated Nov 6, 2024
Information disclosure in the PowerVR kernel driver in Google Android SoC allows local users to read kernel memory via an ioctl. PVRSRVBridgeGetMultiCoreInfo returns output containing uninitialized kernel memory instead of clearing it before copying the result to user space. A low-privileged process on an affected device can invoke the local interface without user interaction and recover sensitive data left in those bytes.
Summary
What happened
Information disclosure in the PowerVR kernel driver in Google Android SoC allows local users to read kernel memory via an ioctl. PVRSRVBridgeGetMultiCoreInfo returns output containing uninitialized kernel memory instead of clearing it before copying the result to user space. A low-privileged process on an affected device can invoke the local interface without user interaction and recover sensitive data left in those bytes.
The record
- CVE
- CVE-2021-0948
- Published
- Jul 12, 2023
- Updated
- Nov 6, 2024
- Vendor
- Product
- Android
- Classifications
- CWE-908
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Nov 6, 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 SoC
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
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