CVE-2025-54912

Published: Sep 9, 2025Modified: Jun 17, 2026

7.8

Vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitability: 1.8 / Impact: 5.9

Source: secure@microsoft.com (Secondary)

Description

Use after free in Windows BitLocker allows an authorized attacker to elevate privileges locally.

Affected (19)

Products: Microsoft: Windows 10 1507, Windows 10 1607, Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 22h2, Windows 11 23h2, Windows 11 24h2, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2022 23h2, Windows Server 2025

15 products

Windows 10 1507

Windows 10 1607

Windows 10 1809

Windows 10 21h2

Windows 10 22h2

Windows 11 22h2

Windows 11 23h2

Windows 11 24h2

Windows Server 2008

Windows Server 2012

Windows Server 2016

Windows Server 2019

Windows Server 2022

Windows Server 2022 23h2

Windows Server 2025

Configuration A

19 vulnerable

Vulnerable Software	Affected Versions
Microsoft Windows 10 1507	version < 10.0.10240.21128
Microsoft Windows 10 1507	version < 10.0.10240.21128
Microsoft Windows 10 1607	version < 10.0.14393.8422
Microsoft Windows 10 1607	version < 10.0.14393.8422
Microsoft Windows 10 1809	version < 10.0.17763.7792
Microsoft Windows 10 1809	version < 10.0.17763.7792
Microsoft Windows 10 21h2	version < 10.0.19044.6332
Microsoft Windows 10 22h2	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 2008	Version r2 sp1
Microsoft Windows Server 2012	All versions
Microsoft Windows Server 2012	Version r2
Microsoft Windows Server 2016	version < 10.0.14393.8422
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

Related CWEs

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.

References (1)

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-54912

Source: secure@microsoft.com

Vendor Advisory

Timeline

No history available yet.