Local memory corruption via procfs registry interface
Published Feb 12, 2020 · Updated Aug 6, 2024
Memory corruption in NVIDIA GPU Display Driver 295.49 allows local users to cause unspecified impact via the Linux procfs registry interface. The public record identifies proc/driver/nvidia/registry as the locus but does not disclose the responsible function or the operation that corrupts memory. Reaching the flaw requires low-privileged local access, while no public source bounds the resulting crash, data access, or code-execution consequences.
Summary
What happened
Memory corruption in NVIDIA GPU Display Driver 295.49 allows local users to cause unspecified impact via the Linux procfs registry interface. The public record identifies proc/driver/nvidia/registry as the locus but does not disclose the responsible function or the operation that corrupts memory. Reaching the flaw requires low-privileged local access, while no public source bounds the resulting crash, data access, or code-execution consequences.
The record
- CVE
- CVE-2012-0951
- Published
- Feb 12, 2020
- Updated
- Aug 6, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA GPU Display Driver
- Classifications
- CWE-787
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 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=29549
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