CVE-2026-64244: drivers/base/memory: set mem->altmap after successful device registration

mediumCVSS 5.5CVE-2026-64244

CSIRTS triage

Other

What: The memory altmap should be set after successful device registration in the memory driver.
Who is affected: Deployments using the memory driver in their systems.
Urgency: Remediation urgency is unclear due to unknown severity and no exploitation reported.
Action: Monitor for updates regarding this issue.

AI-assisted analysis generated from the source advisory — verify against the original.

Details

Source: Microsoft Security Response Center (INTL · vendor-psirt · site)
Severity: medium — CVSS 5.5
Published: 2026-07-14
Exploitation: Not in CISA KEV at last sync

Original advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-64244

Exploitation outlook

EPSS (FIRST.org) estimates each CVE’s probability of exploitation in the next 30 days — here is the CSIRTS.com read on those numbers.

Low exploitation riskCVE-2026-642440.16% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 6% of all scored CVEs.

Referenced CVEs

CVE	CSIRTS overview	External
CVE-2026-64244	coverage & exploitation status	NVD · CVE.org

Same CVEs, other sources

How other CERTs, PSIRTs and databases cover the vulnerabilities in this advisory.

Recent advisories for drivers/base/memory

A cluster of recent advisories against the same product widens the attack surface — attackers routinely chain freshly published CVEs on one product, so review these together.

unknownCVE-2026-64244: In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: set m…nvd · 2026-07-24
unknownCVE-2026-64182: In the Linux kernel, the following vulnerability has been resolved: drivers/base/memory: fix m…nvd · 2026-07-19