NVIDIA libnvrm contains a possible out of bounds read due to a missing bounds check which could lead to local information disclosure.

published 2018-03-12 8y ago modified 2026-06-17 4mo ago also EUVD-2017-15348

cvss: 5.5; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.1%; EPSS 0.1% chance of exploitation in 30 days, percentile 2%
public exploits: 0; none known

NVIDIA libnvrm contains a possible out of bounds read due to a missing bounds check which could lead to local information disclosure. This issue is rated as moderate.Product: Android. Version: N/A. Android: A-64893264. Reference: N-CVE-2017-6287.

Is CVE-2017-6287 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.13% chance of exploitation in the next 30 days, higher than 2% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	5.5	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Affected products

Nvidia Corporation Android

Classification

Weakness

CWE-125 Out-of-bounds Read

References

source.android.com /security/bulletin/pixel/2018-03-01
vendor-advisory

Sources

CVE List CVE-2017-6287
NVD CVE-2017-6287

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.