CVE-2015-2360: Microsoft Win32k Privilege Escalation Vulnerability
Vulnerability summary
CVE-2015-2360 is a high (CVSS 8.8) vulnerability in Microsoft Win32k. It is known to be exploited: CISA lists it, first on 25-05-2022. EPSS estimates a 14.84% chance of exploitation in the next 30 days, higher than 96.6% of scored vulnerabilities.
Timeline
- 10-06-2015PublishedVulnerability first disclosed.
- 25-05-2022Added to CISA KEVMicrosoft Win32k Privilege Escalation Vulnerability
- 15-06-2022CISA remediation dueApply updates per vendor instructions.
- 21-10-2025Last modifiedVulnerability information updated.
Description
win32k.sys in the kernel-mode drivers in Microsoft Windows Server 2003 SP2 and R2 SP2, Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allows local users to gain privileges or cause a denial of service (memory corruption) via a crafted application, aka "Win32k Elevation of Privilege Vulnerability."
CVSS metrics
3 scores · 2 sources · 2 versions- NVDNIST8.8HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS trend
Probability
14.84%
Chance of exploitation in the next 30 days
Percentile
97%
Versus all other CVEs
30-day change
0.00 pp
From 14.84% on 18-09-2026
Known exploited
Compare KEV catalogs- Added
- 25-05-2022
- Federal due date
- 15-06-2022
CISA required action
Apply updates per vendor instructions. nvd.nist.gov/vuln/detail/CVE-2015-2360
Public exploits
0 foundNo public exploits indexed.
Weaknesses
CWE · root cause- CWE-119Improper Restriction of Operations within the Bounds of a Memory BufferThe product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
- CWE-416Use After FreeThe product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Affected systems
1 vendor · 9 products
References
4 links- docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-061Vendor AdvisoryX Refsource MSPatch
- www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2015-2360Government ResourceUS Government Resource