CVE-2025-24052

Windows Agere Modem Driver Elevation of Privilege Vulnerability

HIGH
7.8
CVSS Score
Published: October 14, 2025 at 05:00 PM UTC
Updated: June 17, 2026 at 08:57 AM UTC
17 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 11 Version 25H2 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 11 Version 25H2 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 2%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2116110.0.10240.0 ≤ v < 10.0.10240.2116110.0.10240.0
Affected range stops below 10.0.10240.21161, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.851910.0.14393.0 ≤ v < 10.0.14393.851910.0.14393.0
Affected range stops below 10.0.14393.8519, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.791910.0.17763.0 ≤ v < 10.0.17763.791910.0.17763.0
Affected range stops below 10.0.17763.7919, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.645610.0.19044.0 ≤ v < 10.0.19044.645610.0.19044.0
Affected range stops below 10.0.19044.6456, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.645610.0.19045.0 ≤ v < 10.0.19045.645610.0.19045.0
Affected range stops below 10.0.19045.6456, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.606010.0.22621.0 ≤ v < 10.0.22621.606010.0.22621.0
Affected range stops below 10.0.22621.6060, so it looks safe — our inference, not a vendor statement
v ≤ 10.0.22631.606010.0.22631.0 ≤ v < 10.0.22631.606010.0.22631.0
Affected range stops below 10.0.22631.6060, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.689910.0.26100.0 ≤ v < 10.0.26100.689910.0.26100.0
Affected range stops below 10.0.26100.6899, so it looks safe — our inference, not a vendor statement
v < 10.0.26200.689910.0.26200.0 ≤ v < 10.0.26200.689910.0.26200.0
Affected range stops below 10.0.26200.6899, so it looks safe — our inference, not a vendor statement
6.0.6003.0 ≤ v < 6.0.6003.235716.1.7601.0 ≤ v < 6.1.7601.279746.0.6003.06.1.7601.0r2 sp1sp2
Affected range stops below 6.0.6003.23571, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.7601.27974, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-121

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card