Kernel heap disclosure via ioctl handler race
Published May 8, 2020 · Updated Sep 17, 2024
A race condition in NVIDIA GPU Display Driver before 295.53 allows local users to disclose kernel heap memory through the Linux ioctl interface. The public record locates the race in an ioctl handler but does not identify the raced object or the missing synchronization operation. Exploitation requires high local privileges and a hard-to-win race, and the bounded consequence is kernel-memory disclosure to userspace.
Summary
What happened
A race condition in NVIDIA GPU Display Driver before 295.53 allows local users to disclose kernel heap memory through the Linux ioctl interface. The public record locates the race in an ioctl handler but does not identify the raced object or the missing synchronization operation. Exploitation requires high local privileges and a hard-to-win race, and the bounded consequence is kernel-memory disclosure to userspace.
The record
- CVE
- CVE-2012-0953
- Published
- May 8, 2020
- Updated
- Sep 17, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA GPU Display Driver
- Classifications
- CWE-362, T1005
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2020CVE publishedPublication date reported by the CVE source.
- Sep 17, 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=unspecified <295.53
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