Kernel memory corruption via undersized ioctl buffer
Published May 8, 2020 · Updated Sep 16, 2024
Heap buffer overflow in the NVIDIA GPU Display Driver before 295.53 allows local users to corrupt kernel memory through a device-control ioctl. The NV_ESC_CARD_INFO path accepts an ioctl buffer as small as one byte, allocates the kernel buffer to that size, and then writes 50 bytes per device into it. Reaching the vulnerable ioctl requires high local privileges, and the documented overwrite extends 49 bytes past a one-byte allocation.
Summary
What happened
Heap buffer overflow in the NVIDIA GPU Display Driver before 295.53 allows local users to corrupt kernel memory through a device-control ioctl. The NV_ESC_CARD_INFO path accepts an ioctl buffer as small as one byte, allocates the kernel buffer to that size, and then writes 50 bytes per device into it. Reaching the vulnerable ioctl requires high local privileges, and the documented overwrite extends 49 bytes past a one-byte allocation.
The record
- CVE
- CVE-2012-0952
- Published
- May 8, 2020
- Updated
- Sep 16, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA GPU Display Driver
- Classifications
- CWE-787, CWE-119
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- May 8, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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