CVE-2025-24990: Microsoft Windows Untrusted Pointer Dereference
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-10-14.
- CVSS v3.1 (CVE record)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 9.8%
- higher than 95.6% of all CVEs
- Added to CISA KEV
- 2025-10-14
- US federal due date 2025-11-04
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2025-24990 explained
CVE-2025-24990 is an untrusted pointer dereference vulnerability in the third-party Agere Modem driver (ltmdm64.sys) that ships natively with supported Microsoft Windows versions. Microsoft removed the driver in the October cumulative update. CISA lists the flaw as known to be exploited, so affected systems need prompt patching.
Impact
A local attacker with low privileges can exploit the flaw without user interaction. Successful exploitation can mean high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable, so each attack needs manual steps. Attackers are known to use this vulnerability. Whether it is used in ransomware campaigns is unknown.
Who is affected
Affected builds include Windows 10 Version 1507, 1607, 1809, 21H2 and 22H2, Windows 11 Version 22H2, 23H2, 24H2 and 25H2, Windows Server 2008 R2 Service Pack 1 (including Server Core), and Windows Server 2008 Service Pack 2. Fixed builds include 10.0.19045.6456 (Windows 10 22H2), 10.0.26100.6899 (Windows 11 24H2), 10.0.26200.6899 (Windows 11 25H2) and 6.1.7601.27974 (Server 2008 R2 SP1). The page lists 13 further products.
Written with AI from the data on this page and checked against it automatically.
Official description
Microsoft is aware of vulnerabilities in the third party Agere Modem driver that ships natively with supported Windows operating systems. This is an announcement of the upcoming removal of ltmdm64.sys driver. The driver has been removed in the October cumulative update.
Fax modem hardware dependent on this specific driver will no longer work on Windows. Microsoft recommends removing any existing dependencies on this hardware.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 10 Version 1507x64AffectedFixed in
- < 10.0.10240.21161
- 10.0.10240.21161
- Microsoft Windows 10 Version 1607x64AffectedFixed in
- < 10.0.14393.8519
- 10.0.14393.8519
- Microsoft Windows 10 Version 1809x64AffectedFixed in
- < 10.0.17763.7919
- 10.0.17763.7919
- Microsoft Windows 10 Version 21H2x64AffectedFixed in
- < 10.0.19044.6456
- 10.0.19044.6456
- Microsoft Windows 10 Version 22H2x64AffectedFixed in
- < 10.0.19045.6456
- 10.0.19045.6456
- Microsoft Windows 11 version 22H2x64AffectedFixed in
- < 10.0.22621.6060
- 10.0.22621.6060
- Microsoft Windows 11 Version 23H2x64AffectedFixed in
- < 10.0.22631.6060
- 10.0.22631.6060
- Microsoft Windows 11 Version 24H2x64AffectedFixed in
- < 10.0.26100.6899
- 10.0.26100.6899
- Microsoft Windows 11 Version 25H2AffectedFixed in
- < 10.0.26200.6899
- 10.0.26200.6899
- Microsoft Windows Server 2008 R2 Service Pack 1x64AffectedFixed in
- < 6.1.7601.27974
- 6.1.7601.27974
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 10 Version 1507x64 |
|
|
| Microsoft Windows 10 Version 1607x64 |
|
|
| Microsoft Windows 10 Version 1809x64 |
|
|
| Microsoft Windows 10 Version 21H2x64 |
|
|
| Microsoft Windows 10 Version 22H2x64 |
|
|
| Microsoft Windows 11 version 22H2x64 |
|
|
| Microsoft Windows 11 Version 23H2x64 |
|
|
| Microsoft Windows 11 Version 24H2x64 |
|
|
| Microsoft Windows 11 Version 25H2 |
|
|
| Microsoft Windows Server 2008 R2 Service Pack 1x64 |
|
|
Show 15 more products
- Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64AffectedFixed in
- < 6.1.7601.27974
- 6.1.7601.27974
- Microsoft Windows Server 2008 Service Pack 2x64AffectedFixed in
- < 6.0.6003.23571
- 6.0.6003.23571
- Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)x64AffectedFixed in
- < 6.0.6003.23571
- 6.0.6003.23571
- Microsoft Windows Server 2012x64AffectedFixed in
- < 6.2.9200.25722
- 6.2.9200.25722
- Microsoft Windows Server 2012 (Server Core installation)x64AffectedFixed in
- < 6.2.9200.25722
- 6.2.9200.25722
- Microsoft Windows Server 2012 R2x64AffectedFixed in
- < 6.3.9600.22824
- 6.3.9600.22824
- Microsoft Windows Server 2012 R2 (Server Core installation)x64AffectedFixed in
- < 6.3.9600.22824
- 6.3.9600.22824
- Microsoft Windows Server 2016x64AffectedFixed in
- < 10.0.14393.8519
- 10.0.14393.8519
- Microsoft Windows Server 2016 (Server Core installation)x64AffectedFixed in
- < 10.0.14393.8519
- 10.0.14393.8519
- Microsoft Windows Server 2019x64AffectedFixed in
- < 10.0.17763.7919
- 10.0.17763.7919
- Microsoft Windows Server 2019 (Server Core installation)x64AffectedFixed in
- < 10.0.17763.7919
- 10.0.17763.7919
- Microsoft Windows Server 2022x64AffectedFixed in
- < 10.0.20348.4294
- 10.0.20348.4294
- Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64AffectedFixed in
- < 10.0.25398.1913
- 10.0.25398.1913
- Microsoft Windows Server 2025x64AffectedFixed in
- < 10.0.26100.6899
- 10.0.26100.6899
- Microsoft Windows Server 2025 (Server Core installation)x64AffectedFixed in
- < 10.0.26100.6899
- 10.0.26100.6899
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2x64 |
|
|
| Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012x64 |
|
|
| Microsoft Windows Server 2012 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2012 R2x64 |
|
|
| Microsoft Windows Server 2012 R2 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2016x64 |
|
|
| Microsoft Windows Server 2016 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2019x64 |
|
|
| Microsoft Windows Server 2019 (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2022x64 |
|
|
| Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64 |
|
|
| Microsoft Windows Server 2025x64 |
|
|
| Microsoft Windows Server 2025 (Server Core installation)x64 |
|
|
How to fix it
- Update to the fixed version for your product:
- Microsoft Windows 10 Version 1507: 10.0.10240.21161
- Microsoft Windows 10 Version 1607: 10.0.14393.8519
- Microsoft Windows 10 Version 1809: 10.0.17763.7919
- Microsoft Windows 10 Version 21H2: 10.0.19044.6456
- Microsoft Windows 10 Version 22H2: 10.0.19045.6456
- Microsoft Windows 11 version 22H2: 10.0.22621.6060
- Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24990
- CISA's deadline for US federal agencies: 2025-11-04 (passed) – a useful benchmark for everyone else, too.
What to do
- Install the October cumulative update, which removes the ltmdm64.sys driver, on all affected Windows systems.
- Confirm each system reaches the fixed build for its version, for example
10.0.26100.6899on Windows 11 Version 24H2. - Identify fax modem hardware that depends on the Agere Modem driver; it will stop working after the update.
- Remove existing dependencies on this hardware, as Microsoft recommends.
- Follow the Microsoft advisory and CISA's required action; discontinue use if mitigations are unavailable.
- Check systems for signs of compromise, since attackers are known to exploit this vulnerability.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-822 Untrusted Pointer Dereference
Questions about CVE-2025-24990
- Will fax modems stop working after the update?
- Yes. The October cumulative update removes the ltmdm64.sys driver. Fax modem hardware that depends on this specific driver will no longer work on Windows. Microsoft recommends removing any existing dependencies on this hardware.
- Can it be exploited remotely?
- No. The attack vector is local and requires low privileges, but no user interaction. CISA rates it as not automatable. Attackers are known to use it, so patch promptly.
- What is the deadline for US federal agencies?
- CISA added CVE-2025-24990 to its Known Exploited Vulnerabilities catalog on 2025-10-14. The due date for US federal agencies is 2025-11-04.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.