dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-24052

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.10240.21161 / 10.0.14393.8519 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A vulnerability in the Agere Modem driver (ltmdm64.sys), which shipped natively with supported Windows operating systems, has been addressed by Microsoft removing the driver entirely in the October cumulative update. This third-party fax modem driver was identified as vulnerable, and its removal eliminates the security risk but renders fax modem hardware dependent on ltmdm64.sys non-functional.

MitigationApply the October cumulative Windows update to remove the vulnerable driver, then identify and remove any fax modem hardware dependencies or migrate to alternative fax solutions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.21161
Windows 10 1607Operating system
Affected:< 10.0.14393.8519
Windows 10 1809Operating system
Affected:< 10.0.17763.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:<= 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the vulnerable driver file
    Search for ltmdm64.sys in the Windows\System32\drivers directory and the driver store using: Get-ChildItem -Path C:\Windows -Filter ltmdm64.sys -Recurse -ErrorAction SilentlyContinue
    Affected if The file ltmdm64.sys exists on the system in any location
  2. Check Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the exact Windows build number
    Affected if The installed Windows version and build number fall within the affected ranges: Windows 10 1507 < 10.0.10240.21161, 1607 < 10.0.14393.8519, 1809 < 10.0.17763.7919, 21h2 < 10.0.19044.6456, 22h2 < 10.0.19045.6456; Windows 11 22h2 < 10.0.22621.6060, 23h2 <= 10.0.22631.6060, 24h2 < 10.0.26100.6899
  3. Verify driver presence in device manager
    Open Device Manager, select 'Show hidden devices', and look under 'Modems' or 'Other devices' for any Agere or generic fax modem entries that reference ltmdm64.sys
    Affected if A fax modem device using ltmdm64.sys is listed as a hardware component
  4. Check driver loaded in memory
    Run 'driverquery /v | findstr ltmdm64' or 'sc query type= driver' to list loaded drivers and search for ltmdm64 in the output
    Affected if The ltmdm64 driver appears in the list of loaded kernel drivers

The system is affected if ltmdm64.sys is present on the disk or loaded and the Windows version falls within one of the affected build ranges before the October cumulative update.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.21161 / 10.0.14393.8519 / 10.0.17763.7919 or later
Fixed in 10.0.10240.2116110.0.14393.851910.0.17763.7919
Interim mitigation

Apply the October cumulative Windows update to remove the vulnerable driver, then identify and remove any fax modem hardware dependencies or migrate to alternative fax solutions.

Recommended fix High confidence

October cumulative update (minimum build versions: Win10 1507: 10.0.10240.21161 | Win10 1607: 10.0.14393.8519 | Win10 1809: 10.0.17763.7919 | Win10 21h2: 10.0.19044.6456 | Win10 22h2: 10.0.19045.6456 | Win11 22h2: 10.0.22621.6060 | Win11 23h2: >10.0.22631.6060 | Win11 24h2: 10.0.26100.6899)

  1. Open Windows Update settings on the affected system
  2. Check for and install the October cumulative update (or later) for your Windows version
  3. Verify the update installed successfully by checking Windows Update history
  4. Confirm ltmdm64.sys driver has been removed - it should no longer be present in C:\Windows\System32\drivers\
  5. If fax modem functionality is required, migrate to alternative solutions as the driver is no longer available
Caveat Fax modem hardware dependent on the ltmdm64.sys driver will no longer function - the driver has been removed as part of the security update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24052 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24052 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data