CVE-2023-40547

How to fix it

Microsoft lists 31 affected products and the update that fixes each:

• KB5041592 · fixed build 10.0.22000.3147
  Windows 11 version 21H2 for ARM64-based Systems, Windows 11 version 21H2 for x64-based Systems
• KB5055518 · fixed build 10.0.19045.5737, 10.0.19044.5737
  Windows 10 Version 22H2 for 32-bit Systems, Windows 10 Version 22H2 for ARM64-based Systems, Windows 10 Version 22H2 for x64-based Systems, Windows 10 Version 21H2 for x64-based Systems, Windows 10 Version 21H2 for ARM64-based Systems, and 1 more
• KB5055519 · fixed build 10.0.17763.7136
  Windows Server 2019 (Server Core installation), Windows Server 2019, Windows 10 Version 1809 for x64-based Systems, Windows 10 Version 1809 for 32-bit Systems
• KB5055521 · fixed build 10.0.14393.7969
  Windows Server 2016 (Server Core installation), Windows Server 2016, Windows 10 Version 1607 for x64-based Systems, Windows 10 Version 1607 for 32-bit Systems
• KB5055523 · fixed build 10.0.26100.3775
  Windows 11 Version 24H2 for ARM64-based Systems
• KB5055526 · fixed build 10.0.20348.3453
  Windows Server 2022 (Server Core installation), Windows Server 2022
• KB5055527 · fixed build 10.0.25398.1551
  Windows Server 2022, 23H2 Edition (Server Core installation)
• KB5055528 · fixed build 10.0.22621.5189, 10.0.22631.5189
  Windows 11 Version 24H2 for x64-based Systems, Windows 11 Version 23H2 for x64-based Systems, Windows 11 Version 23H2 for ARM64-based Systems, Windows 11 Version 22H2 for x64-based Systems, Windows 11 Version 22H2 for ARM64-based Systems
• KB5055547 · fixed build 10.0.10240.20978
  Windows 10 for x64-based Systems, Windows 10 for 32-bit Systems
• KB5055557 · fixed build 6.3.9600.22523
  Windows Server 2012 R2 (Server Core installation), Windows Server 2012 R2
• KB5055581 · fixed build 6.2.9200.25423
  Windows Server 2012 (Server Core installation), Windows Server 2012

What Microsoft changed

• September 19, 2024: Updated FAQs with the following information: To address a known issue on systems with dual booting for Windows and Linux, we have reconfigured the manner in which this fix can be applied. Starting with the September 10, 2024 security updates, the fix will not automatically apply the SBAT update to the firmware. Customers who have applied the August 13, 2024 security updates will have the SBAT update in firmware and will be protected. Customers who have devices with Windows system only and who have not applied the August updates and who want to be protected from this issue can either apply the August 13, 2024 updates or apply the September 10, 2024 updates and set the following registry key from an Administrator command prompt: reg add HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Secureboot /v AvailableUpdates /t REG_DWORD /d 0x400 /f”
• August 13, 2024: Information published.
• May 16, 2025: In the Security Updates table, updated Download and Article links for all supported versions of Windows to the security updates released on May 13, 2025. These updates apply improvements to SBAT for the detection of Linux systems, and address the known issue with dual booting for Windows and Linux. Customers who experienced issues with dual booting Windows and Linux should install the May 13, 2025 security updates. Customers whose systems are configured to receive automatic updates do not need to take any further action.

Details

Weakness

CWE-122: Heap-based Buffer Overflow

Publicly disclosed (Microsoft)

No

Exploited (Microsoft)

No

Known exploited (CISA KEV)

Not listed

Published

August 13, 2024

Last revised

May 16, 2025

Get told when this changes

Senserva Watch emails Microsoft security and patch alerts when something moves: a new exploitation report, a revised fix, a known issue. Free, one email address.

Join Senserva Watch

References