PatchSiren cyber security CVE debrief
CVE-2017-0321 Freebsd CVE debrief
CVE-2017-0321 describes a kernel-mode NULL pointer dereference in NVIDIA GPU Display Driver handling of invalid user input. The issue is high severity and can result in denial of service, with potential impact beyond availability because NVD records a changed security scope and high confidentiality, integrity, and availability impact in its CVSS vector. The CVE was published on 2017-02-15. NVD’s affected-platform data points to the NVIDIA GPU driver, while other platform CPEs in the record are marked not vulnerable.
- Vendor
- Freebsd
- Product
- CVE-2017-0321
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2017-02-15
- Original CVE updated
- 2026-05-13
- Advisory published
- 2017-02-15
- Advisory updated
- 2026-05-13
Who should care
Administrators and security teams managing systems with NVIDIA GPU Display Driver installations should care, especially where local users can reach the affected kernel-mode path. Fleet owners for workstations, desktops, VDI, and servers using NVIDIA graphics drivers should prioritize review of vendor guidance and remediation.
Technical summary
NVD describes the flaw as a NULL pointer dereference caused by invalid user input in the kernel mode layer handler. The official record lists NVIDIA GPU driver as vulnerable and identifies CWE-476. The CVSS v3.0 vector is AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H, indicating a local attack requiring low privileges and no user interaction, with changed scope and high impact. NVD also includes non-vulnerable CPE entries for FreeBSD, Linux kernel, Microsoft Windows, and Oracle Solaris in the same record.
Defensive priority
High. Because the attack is local and low-complexity, exposure depends on whether an untrusted local user can reach the driver path. The potential for denial of service and privilege-related impact makes this worth prompt patch and exposure review on affected endpoints.
Recommended defensive actions
- Check whether any deployed systems use NVIDIA GPU Display Driver versions covered by the vendor advisory and NVD record.
- Apply the NVIDIA security update or vendor-recommended remediation referenced by the official advisory.
- Restrict local access where practical, especially on multi-user systems that expose the driver to untrusted users.
- Prioritize patching on systems where local users, shared sessions, or VDI users may interact with the affected driver.
- Validate remediation by confirming the installed NVIDIA driver build matches the vendor's fixed release guidance.
Evidence notes
Source corpus shows the official CVE record and NVD detail page, plus an NVIDIA vendor advisory reference (http://nvidia.custhelp.com/app/answers/detail/a_id/4398). The NVD metadata lists cpe:2.3:a:nvidia:gpu_driver:-:*:*:*:*:*:*:* as vulnerable and marks FreeBSD, Linux kernel, Microsoft Windows, and Oracle Solaris CPEs as not vulnerable. The record assigns CWE-476 and CVSS v3.0 AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. The vendor field in the supplied data is inconsistent with the vulnerable CPE and should be treated cautiously.
Official resources
-
CVE-2017-0321 CVE record
CVE.org
-
CVE-2017-0321 NVD detail
NVD
-
Source item URL
nvd_modified
-
Mitigation or vendor reference
[email protected] - Vendor Advisory
Published on 2017-02-15. Later metadata updates in NVD do not change the original CVE publication date.