CVE-2017-6296
CVE-2017-6296 is a high-severity vulnerability in Nvidia Shield Tv Firmware with a CVSS 3.x base score of 7.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-362.
Key facts
- Severity: High (CVSS 3.x base score 7.0)
- CVSS v2: 4.4
- EPSS exploit prediction: 0% (1st percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-362
- Affected product: Nvidia Shield Tv Firmware
- Published:
- Last modified:
Description
NVIDIA TrustZone Software contains a TOCTOU issue in the DRM application which may lead to the denial of service or possible escalation of privileges. This issue is rated as moderate.
Frequently asked questions
- What is CVE-2017-6296?
- NVIDIA TrustZone Software contains a TOCTOU issue in the DRM application which may lead to the denial of service or possible escalation of privileges. This issue is rated as moderate.
- How severe is CVE-2017-6296?
- CVE-2017-6296 has a CVSS 3.x base score of 7.0, rated high severity. It is exploitable over local access with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2017-6296 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (1st percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2017-6296?
- CVE-2017-6296 primarily affects Nvidia Shield Tv Firmware. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2017-6296?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2017-6296 published?
- CVE-2017-6296 was published on 2018-03-06 and last updated on 2026-06-17.
References
Affected products (2)
- cpe:2.3:o:nvidia:shield_tv_firmware:*:*:*:*:*:*:*:*
- cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
More vulnerabilities in Nvidia Shield Tv Firmware
- CVE-2017-6295 — High (CVSS 8.4): NVIDIA TrustZone Software contains a vulnerability in the Keymaster implementation where the software reads data past…
- CVE-2017-6282 — High (CVSS 7.8): NVIDIA Tegra kernel driver contains a vulnerability in NVMAP where an attacker has the ability to write an arbitrary…
- CVE-2016-6915 — High (CVSS 7.8): Stack-based buffer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield…
- CVE-2016-6917 — High (CVSS 7.8): Buffer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before…
- CVE-2016-6916 — High (CVSS 7.8): Integer overflow in nvhost_job.c in the NVIDIA video driver for Android, Shield TV before OTA 3.3, Shield Table before…
- CVE-2017-6284 — Medium (CVSS 5.5): NVIDIA Security Engine contains a vulnerability in the Deterministic Random Bit Generator (DRBG) where the DRBG does…
All CVEs affecting Nvidia Shield Tv Firmware →
Other CWE-362 (Race Condition) vulnerabilities
- CVE-2022-27626 — Critical (CVSS 10.0): A vulnerability regarding concurrent execution using shared resource with improper synchronization ('Race Condition')…
- CVE-2015-8556 — Critical (CVSS 10.0): Local privilege escalation vulnerability in the Gentoo QEMU package before 2.5.0-r1.
- CVE-2014-0703 — Critical (CVSS 10.0): Cisco Wireless LAN Controller (WLC) devices 7.4 before 7.4.110.0 distribute Aironet IOS software with a race condition…
- CVE-2010-1228 — Critical (CVSS 10.0): Multiple race conditions in the sandbox infrastructure in Google Chrome before 4.1.249.1036 have unspecified impact and…
- CVE-2008-6598 — Critical (CVSS 10.0): Multiple race conditions in WANPIPE before 3.3.6 have unknown impact and attack vectors related to "bri restart logic."
- CVE-2026-46137 — Critical (CVSS 9.8): In the Linux kernel, the following vulnerability has been resolved: mptcp: pm: ADD_ADDR rtx: fix potential…