# CVE-2025-24990: Microsoft Windows Untrusted Pointer Dereference

> Attackers can exploit the Agere Modem driver to gain elevated privileges on Windows systems, prompting Microsoft to remove the driver in recent updates.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 14 Oct 2025 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Oct 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-9g9x-fc99-93r6

## What is CVE-2025-24990?

CVE-2025-24990 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 14 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-822 (Untrusted Pointer Dereference)

## Which versions are affected by CVE-2025-24990?

It affects 16 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows 11 24h2, Microsoft Windows 11 25h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2, Microsoft Windows Server 2025.

## How do I fix CVE-2025-24990?

No fix has been published for CVE-2025-24990 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 4 Nov 2025.

## Is CVE-2025-24990 being exploited?

Yes. Attackers have exploited CVE-2025-24990 in the wild since at least 14 Oct 2025.

Public exploit code:

- Proof of Concept CVE-2025-24990 (Agere Systems's driver)  (github_poc): https://github.com/moiz-2x/CVE-2025-24990_POC
- CVE-2025-24990 Research writeup (github_poc): https://github.com/sentinel-aidefense/CVE-2025-24990

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24990 and fix it if it is affected.

What it is: CVE-2025-24990 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 14 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-24990 in the wild since at least 14 Oct 2025.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-24990/ (Markdown: https://insights.sbomify.com/CVE-2025-24990/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-24990
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-24990
- OSV: https://osv.dev/vulnerability/CVE-2025-24990

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-24990/
Summaries are generated and may contain mistakes; the official description above is the record.