# CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid

> A Linux kernel bug in DAMON migration causes folios to remain isolated, leading to memory leaks and potential denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Aug 2026
- **Updated:** 23 Aug 2026
- **Also known as:** BELL-CVE-2026-74644, DEBIAN-CVE-2026-74644, GHSA-m6xx-fpfc-5x79, UBUNTU-CVE-2026-74644

## What is CVE-2026-74644?

CVE-2026-74644 is a memory corruption vulnerability in Linux, published on 22 Aug 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

mm/damon/ops-common: putback folios on invalid migrate nid

damon_pa_migrate() and damos_va_migrate() isolate folios into a local list
and then call damon_migrate_pages().  When target_nid is invalid
(including the scheme default NUMA_NO_NODE / -1), damon_migrate_pages()
returns early without putting the folios back to the LRU.

Callers then discard the list head while those folios remain isolated with
an extra reference taken by folio_isolate_lru().  The pages stay off the
LRU for as long as the mapping exists (anon active+inactive counts drop
while RSS does not), and the leftover references can pin the pages after
the mapping is gone.

Put the folios back on the invalid-nid path so ignored migration requests
still return them to the LRU.

## Which versions are affected by CVE-2026-74644?


## How do I fix CVE-2026-74644?

Apply the vendor's patch.

## Is CVE-2026-74644 being exploited?

There is no known exploitation of CVE-2026-74644 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-74644 and fix it if it is affected.

What it is: CVE-2026-74644 is a memory corruption vulnerability in Linux, published on 22 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-74644 in the wild and no public exploit code.

Affected product: Linux. 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-2026-74644/ (Markdown: https://insights.sbomify.com/CVE-2026-74644/index.md)
```

## Sources

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

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