7

CVE-2025-29841

Concurrent execution using shared resource with improper synchronization ('race condition') in Universal Print Management Service allows an authorized attacker to elevate privileges locally.

Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
This information is available to logged-in users.
Data is provided by the National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 21h2 HwPlatformarm64 Version < 10.0.19044.5854
Microsoft ≫ Windows 10 21h2 HwPlatformx64 Version < 10.0.19044.5854
Microsoft ≫ Windows 10 21h2 HwPlatformx86 Version < 10.0.19044.5854
Microsoft ≫ Windows 10 22h2 HwPlatformarm64 Version < 10.0.19045.5854
Microsoft ≫ Windows 10 22h2 HwPlatformx64 Version < 10.0.19045.5854
Microsoft ≫ Windows 10 22h2 HwPlatformx86 Version < 10.0.19045.5854
Microsoft ≫ Windows 11 22h2 HwPlatformarm64 Version < 10.0.22621.5335
Microsoft ≫ Windows 11 22h2 HwPlatformx64 Version < 10.0.22621.5335
Microsoft ≫ Windows 11 23h2 HwPlatformarm64 Version < 10.0.22631.5335
Microsoft ≫ Windows 11 23h2 HwPlatformx64 Version < 10.0.22631.5335
Microsoft ≫ Windows 11 24h2 HwPlatformarm64 Version < 10.0.26100.4061
Microsoft ≫ Windows 11 24h2 HwPlatformx64 Version < 10.0.26100.4061
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.3692
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1611
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.4061
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Type Source Score Percentile
EPSS FIRST.org 0.08% 0.233
CVSS Metriken
Source 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.