CVE-2026-74644: mm/damon/ops-common: putback folios on invalid migrate nid
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
- Fixed version: Linux Linux 460181e4bb47a57776c64f0832c2096de8878cb3, 5deb65c34e682e7c5f5df417a70e223e8fcc5f5a, 6.12.105.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 460181e4bb47a57776c64f0832c2096de8878cb3, 5deb65c34e682e7c5f5df417a70e223e8fcc5f5a, 6.12.105 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Aug 22, 2026
- Updated
- Oct 14, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 9d0c2d15aff96746f99a7c97221bb8ce5b62db19, 6.17affected
- 7c303fa1f311aadc17fa82b7bbf776412adf45de and later · before 7001c0a1bc9018cd5b2b72ebebb216d738b2ec81affected · git
- 7e6c3130690a01076efdf45aa02ba5d5c16849a0 and later · before 460181e4bb47a57776c64f0832c2096de8878cb3affected · git
- 7e6c3130690a01076efdf45aa02ba5d5c16849a0 and later · before cfef454862b7d2776e0955b873dd59af6b47cfcbaffected · git
- 7e6c3130690a01076efdf45aa02ba5d5c16849a0 and later · before 5deb65c34e682e7c5f5df417a70e223e8fcc5f5aaffected · git
- 6.12.44 and later · before 6.12.105affected · semver
- 6.16.4 and later · before 6.17affected · semver
- before 6.17not affected · semver
- 6.12.105 and later · up to and including 6.12.*not affected · semver
- 6.18.45 and later · up to and including 6.18.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.9-1 | 7.1.9-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74642Aug 22, 2026 · ALSA: usb: Fix UAF at delayed release of MIDI2 EPs0Monitor
- ← EarlierCVE-2026-74643Aug 22, 2026 · samples/damon/mtier: error out for zero quota goal target values0Monitor
- Later →CVE-2026-74645Aug 22, 2026 · mm/damon/lru_sort: error out for >10000 active_mem_bp0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 460181e4bb47a57776c64f0832c2096de8878cb3 | Vendor (CNA) |
| Linux Linux | 5deb65c34e682e7c5f5df417a70e223e8fcc5f5a | Vendor (CNA) |
| Linux Linux | 6.12.105 | Vendor (CNA) |
| Linux Linux | 6.17 | Vendor (CNA) |
| Linux Linux | 7001c0a1bc9018cd5b2b72ebebb216d738b2ec81 | Vendor (CNA) |
| Linux Linux | cfef454862b7d2776e0955b873dd59af6b47cfcb | Vendor (CNA) |
| debian:linux | 6.12.105-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0893 · Aug 24, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.