CVE-2017-6248

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

An elevation of privilege vulnerability in the NVIDIA sound driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process. Product: Android. Versions: N/A. Android ID: A-34372667. References: N-CVE-2017-6248.

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
50.7%
KEV
Not listed

Published

July 6, 2017

Last Modified

May 13, 2026

Frequently asked(5)

What is CVE-2017-6248?
CVE-2017-6248 is a high vulnerability published on July 6, 2017. An elevation of privilege vulnerability in the NVIDIA sound driver could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Moderate because it first requires compromising a privileged process. Product: Android. Versions: N/A.…
When was CVE-2017-6248 disclosed?
CVE-2017-6248 was first published in the National Vulnerability Database on July 6, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-6248 actively exploited?
CVE-2017-6248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-6248?
CVE-2017-6248 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2017-6248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-6248, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-6248

Explore →

Is Your Infrastructure Affected by CVE-2017-6248?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.