Skip to content
Fencer Vulns
high 7.8

CVE-2025-24052 json

Windows Agere Modem Driver Elevation of Privilege Vulnerability

published 2025-10-14 12 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-34425

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 85%
public exploits
0
none known

Summary

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.

Patch / fix

  • 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
  • Microsoft Windows 11 Version 23H2 10.0.22631.6060
  • Microsoft Windows 11 Version 24H2 10.0.26100.6899
  • Microsoft Windows 11 Version 25H2 10.0.26200.6899
  • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.27974
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.27974
  • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.23571
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.23571
  • Microsoft Windows Server 2012 6.2.9200.25722
  • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.25722
  • Microsoft Windows Server 2012 R2 6.3.9600.22824
  • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.22824
  • Microsoft Windows Server 2016 10.0.14393.8519
  • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.8519
  • Microsoft Windows Server 2019 10.0.17763.7919
  • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.7919
  • Microsoft Windows Server 2022 10.0.20348.4294
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation) 10.0.25398.1913
  • Microsoft Windows Server 2025 10.0.26100.6899
  • Microsoft Windows Server 2025 (Server Core installation) 10.0.26100.6899

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
12 mo ago

Exploit prediction

2.54% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:P/RL:O/RC:C
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Windows 10 Version 1507
  • Microsoft Windows 10 Version 1607
  • Microsoft Windows 10 Version 1809
  • Microsoft Windows 10 Version 21H2
  • Microsoft Windows 10 Version 22H2
  • Microsoft Windows 11 version 22H2
  • Microsoft Windows 11 Version 23H2
  • Microsoft Windows 11 Version 24H2
  • Microsoft Windows 11 Version 25H2
  • Microsoft Windows Server 2008 R2 Service Pack 1
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)
  • Microsoft Windows Server 2008 Service Pack 2
  • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation)
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 (Server Core installation)
  • Microsoft Windows Server 2012 R2
  • Microsoft Windows Server 2012 R2 (Server Core installation)
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2016 (Server Core installation)
  • Microsoft Windows Server 2019
  • Microsoft Windows Server 2019 (Server Core installation)
  • Microsoft Windows Server 2022
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)
  • Microsoft Windows Server 2025
  • Microsoft Windows Server 2025 (Server Core installation)

Classification

Weakness
  • CWE-121 Stack-based Buffer Overflow

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.