Service interruption via kernel null-pointer dereference
Published Nov 18, 2022 · Updated Apr 29, 2025
NULL pointer dereference in NVIDIA GPU Display Driver for Windows and Linux allows local users to interrupt service. The kernel-mode layer reaches a null-pointer dereference in response to a local user's action, but NVIDIA has not disclosed the responsible handler or input path. Basic local user capabilities are required, and successful exploitation has no reported confidentiality or integrity impact.
Summary
What happened
NULL pointer dereference in NVIDIA GPU Display Driver for Windows and Linux allows local users to interrupt service. The kernel-mode layer reaches a null-pointer dereference in response to a local user's action, but NVIDIA has not disclosed the responsible handler or input path. Basic local user capabilities are required, and successful exploitation has no reported confidentiality or integrity impact.
The record
- CVE
- CVE-2022-34665
- Published
- Nov 18, 2022
- Updated
- Apr 29, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 18, 2022CVE publishedPublication date reported by the CVE source.
- Apr 29, 2025Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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