7
CVE-2025-62573
- EPSS 0.05%
- Veröffentlicht 09.12.2025 17:55:43
- Zuletzt bearbeitet 10.12.2025 19:17:02
- Quelle secure@microsoft.com
- CVE-Watchlists
- Unerledigt
Use after free in Windows DirectX allows an authorized attacker to elevate privileges locally.
Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1607 HwPlatformx64 Version < 10.0.14393.8688
Microsoft ≫ Windows 10 1607 HwPlatformx86 Version < 10.0.14393.8688
Microsoft ≫ Windows 10 1809 HwPlatformx64 Version < 10.0.17763.8146
Microsoft ≫ Windows 10 1809 HwPlatformx86 Version < 10.0.17763.8146
Microsoft ≫ Windows 10 21h2 Version < 10.0.19044.6691
Microsoft ≫ Windows 10 22h2 Version < 10.0.19045.6691
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.6345
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.7392
Microsoft ≫ Windows 11 25h2 Version < 10.0.26200.7392
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.8688
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.8146
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.4467
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.2025
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.7392
| Typ | Quelle | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.05% | 0.154 |
| Quelle | Base Score | Exploit Score | Impact Score | Vector String |
|---|---|---|---|---|
| secure@microsoft.com | 7 | 1 | 5.9 |
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/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.