Actively exploited

CVE-2025-24990 Microsoft Windows Untrusted Pointer Dereference Vulnerability

Microsoft Windows Agere Modem Driver contains an untrusted pointer dereference vulnerability that allows for privilege escalation. An attacker who successfully exploited this vulnerability could gain administrator privileges.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 14 Oct 2025.
  • Rated High severity (CVSS 7.8, scored by Vendor).
  • It has been in the catalogue for 388 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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 Versions

ProductVersions
Microsoft Windows 10 Version 150710.0.10240.0 to before 10.0.10240.21161
Microsoft Windows 10 Version 160710.0.14393.0 to before 10.0.14393.8519
Microsoft Windows 10 Version 180910.0.17763.0 to before 10.0.17763.7919
Microsoft Windows 10 Version 21H210.0.19044.0 to before 10.0.19044.6456
Microsoft Windows 10 Version 22H210.0.19045.0 to before 10.0.19045.6456
Microsoft Windows 11 version 22H210.0.22621.0 to before 10.0.22621.6060

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-24990 and every other exploited flaw on the list.

Check My Exposure