The kernel in Microsoft Windows 8.1, Windows Server 2012 R2, Windows RT 8.1, and Windows 10 Gold and 1511 allows local users to bypass the…

published 2015-11-11 10y ago modified 2026-06-17 4mo ago also EUVD-2015-6052

cvss: 2.1; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.1%; EPSS 3.1% chance of exploitation in 30 days, percentile 88%
public exploits: 0; none known

The kernel in Microsoft Windows 8.1, Windows Server 2012 R2, Windows RT 8.1, and Windows 10 Gold and 1511 allows local users to bypass the KASLR protection mechanism, and consequently discover a driver base address, via a crafted application, aka "Windows Kernel Memory Information Disclosure Vulnerability."

Patch / fix

links 1

docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-115 advisory

Is CVE-2015-6109 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

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

CVSS scores

assigned by	version	score	vector
NVD	2.0	2.1	AV:L/AC:L/Au:N/C:P/I:N/A:N

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

docs.microsoft.com /en-us/security-updates/securitybulletins/2015/ms15-115
vendor-advisory, patch
securitytracker.com /id/1034114
vdb-entry, third-party-advisory

Sources

CVE List CVE-2015-6109
NVD CVE-2015-6109

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.