Local denial of service via reachable firmware assertion
Published Jul 22, 2021 · Updated Aug 3, 2024
Reachable assertion in NVIDIA GPU Display Driver firmware allows local users to crash Windows or Linux systems by triggering the check. The firmware executes an assert() or equivalent terminating check on an attacker-reachable condition instead of handling that condition safely. NVIDIA has not disclosed the trigger path or input; local access is required, with no prior privileges or user interaction, and impact is limited to exit, denial of service, or system crash.
Summary
What happened
Reachable assertion in NVIDIA GPU Display Driver firmware allows local users to crash Windows or Linux systems by triggering the check. The firmware executes an assert() or equivalent terminating check on an attacker-reachable condition instead of handling that condition safely. NVIDIA has not disclosed the trigger path or input; local access is required, with no prior privileges or user interaction, and impact is limited to exit, denial of service, or system crash.
The record
- CVE
- CVE-2021-1093
- Published
- Jul 22, 2021
- Updated
- Aug 3, 2024
- Vendor
- NVIDIA
- Product
- NVIDIA GPU Display Driver
- Classifications
- CWE-404, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 22, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=All GPU Driver versions
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