7.8
CVE-2025-55224
- EPSS 0.04%
- Published 09.09.2025 17:01:31
- Last modified 12.09.2025 14:53:22
- Source secure@microsoft.com
- Teams watchlist Login
- Open Login
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Win32K - GRFX allows an authorized attacker to execute code locally.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
This information is available to logged-in users. Login
Data is provided by the National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1809 HwPlatformx64 Version < 10.0.17763.7792
Microsoft ≫ Windows 10 21h2 HwPlatformx64 Version < 10.0.19044.6332
Microsoft ≫ Windows 10 22h2 HwPlatformx64 Version < 10.0.19045.6332
Microsoft ≫ Windows 11 22h2 Version < 10.0.22621.5909
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.5909
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.6508
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.7792
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.4106
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1849
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.6508
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.04% | 0.115 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
secure@microsoft.com | 7.8 | 1.1 | 6 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
|
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-416 Use After Free
The 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.