CVE-2025-24990
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 · uneditedMicrosoft 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 confidenceA vulnerable Agere modem driver (ltmdm64.sys) that shipped natively with supported Windows operating systems has been removed in the October cumulative update. The driver contained security vulnerabilities (CVSS 7.8) that could be exploited, prompting Microsoft to remove it entirely rather than patch it. Any fax modem hardware dependent on this specific driver will no longer function.
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< 10.0.10240.21161< 10.0.14393.8519< 10.0.17763.7919< 10.0.19044.6456< 10.0.19045.6456< 10.0.22621.6060<= 10.0.22631.6060< 10.0.26100.6899CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if ltmdm64.sys driver file existsSearch for the file ltmdm64.sys in system directories. Typical paths include C:\Windows\System32\drivers\ and C:\Windows\System32\DriverStore\. Use: Get-ChildItem -Path C:\Windows -Recurse -Filter ltmdm64.sys -ErrorAction SilentlyContinueAffected if The driver file is present on the system
-
Verify Windows build numberRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the Windows build numberAffected if The build number falls within the affected ranges: < 10.0.10240.21161 (1507), < 10.0.14393.8519 (1607), < 10.0.17763.7919 (1809), < 10.0.19044.6456 (21h2), < 10.0.19045.6456 (22h2), < 10.0.22621.6060 (Win11 22h2), <= 10.0.22631.6060 (Win11 23h2), < 10.0.26100.6899 (Win11 24h2)
-
Confirm driver is loaded or present in driver storeRun 'driverquery /v | findstr ltmdm64' or check registry under HKLM\SYSTEM\CurrentControlSet\Services\ltmdm64 for the presence of this driverAffected if The driver is listed as installed or loaded in the system driver database
The system is affected if the ltmdm64.sys driver file exists and the Windows build number is within any of the affected version ranges listed.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2116110.0.14393.851910.0.17763.7919
Organizations should inventory systems for Agere modem hardware dependencies and remove the driver or replace the hardware before the update deploys. Microsoft recommends eliminating dependencies on this hardware entirely as no replacement driver is being provided.
October cumulative update for respective Windows version (Windows 10 1507: 10.0.10240.21161, Windows 10 1607: 10.0.14393.8519, Windows 10 1809: 10.0.17763.7919, Windows 10 21h2: 10.0.19044.6456, Windows 10 22h2: 10.0.19045.6456, Windows 11 22h2: 10.0.22621.6060, Windows 11 23h2: 10.0.22631.6060, Win
- Install the October cumulative update (or later) for your Windows version via Windows Update or Microsoft Update Catalog
- Restart the system after applying the update
- Verify the ltmdm64.sys driver has been removed by checking Device Manager or running 'driverquery /v | findstr ltmdm64'
- If fax modem hardware dependent on this driver no longer functions, this is expected behavior - Microsoft recommends removing dependencies on this hardware
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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