CVE-2024-43526: Windows Mobile Broadband Driver Remote Code Execution Vulnerability
Windows Mobile Broadband Driver Remote Code Execution Vulnerability
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22621.4317Patch KB5044285 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.19044.5011Patch KB5044273 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.19045.5011Patch KB5044273 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.2033Patch KB5044284 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.25398.1189Patch KB5044288 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22631.4317Patch KB5044285 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.17763.6414Patch KB5044277 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.22000.3260Patch KB5044280
Event History
Frequently Asked Questions
What is the severity of CVE-2024-43526?
CVE-2024-43526 is classified as a critical vulnerability that allows remote code execution.
Which versions of Windows are affected by CVE-2024-43526?
CVE-2024-43526 affects multiple versions of Windows, including Windows 10 (21H2 and 22H2), Windows 11 (21H2, 22H2, and 23H2), and Windows Server 2019.
How do I fix CVE-2024-43526?
To fix CVE-2024-43526, ensure that you apply the latest security patches available from Microsoft, specifically KB5044280, KB5044273, or KB5044277 depending on your system.
What can happen if CVE-2024-43526 is exploited?
Exploitation of CVE-2024-43526 can allow an attacker to execute arbitrary code on the affected Windows system.
Is there a workaround for CVE-2024-43526 until a patch is applied?
Currently, there is no known workaround for CVE-2024-43526; applying the patch is the recommended action.