# CVE-2026-64180 — Linux

> As of 2026-07-19, CVE-2026-64180 is a vulnerability in Linux, EPSS 0.1% (5.2th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-64180 as of 2026-07-19; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-07-19

## What is CVE-2026-64180?

In the Linux kernel, the following vulnerability has been resolved: mm/memory_hotplug: fix memory block reference leak on remove Patch series "mm: Fix memory block leaks and locking", v2. This series fixes two memory block device reference leaks and one locking issue around the per-memory_block hwpoison counter. This patch (of 2): remove_memory_blocks_and_altmaps() looks up each memory block with find_memory_block(), which acquires a reference to the memory block device. That reference is never dropped on this path, resulting in a leaked device reference when removing memory blocks and their altmaps. Drop the reference after retrieving mem->altmap and clearing mem->altmap, before removing the memory block device.

1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 78 days ago.

## Severity and exploitation probability

- **EPSS (FIRST):** 0.1% probability of exploitation in the next 30 days, higher than 5.2% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-07-19

## Is CVE-2026-64180 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

## Affected products and versions

- [Linux](https://intel.threadlinqs.com/vendors/linux): Linux

## How to fix CVE-2026-64180

No vendor patch reference has been recorded for CVE-2026-64180 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-64180

No threat campaign in the Threadlinqs corpus currently references CVE-2026-64180, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on 2026-07-21. This product uses the NVD API but is not endorsed or certified by the NVD.

**Other references**

- [git.kernel.org](https://git.kernel.org/stable/c/b8ab30c79fc00147125b9c39f928561d9dd13d06)
- [git.kernel.org (09ce923071e7852ece60d7368e05249bf32c7967)](https://git.kernel.org/stable/c/09ce923071e7852ece60d7368e05249bf32c7967)
- [git.kernel.org (df64c0d21c3f85f844b2f656333e43d97e6ffa74)](https://git.kernel.org/stable/c/df64c0d21c3f85f844b2f656333e43d97e6ffa74)
- [git.kernel.org (93866f55f7e292fe3d47d36c9efe5ee10213a06b)](https://git.kernel.org/stable/c/93866f55f7e292fe3d47d36c9efe5ee10213a06b)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-64180
Full detection coverage and IOCs for threats exploiting CVE-2026-64180 via the Threadlinqs MCP server (Purple tier): https://intel.threadlinqs.com/mcp