In the Linux kernel, the following vulnerability has been resolved: mm/memory: fix spurious warning when unmapping device-private/exclusive pages… (CVE-2026-64131)
A vulnerability in the Linux kernel's memory management subsystem caused spurious warnings when unmapping device-private or exclusive pages. This issue arises from an incorrect condition check between anonymous folios and anonymous VMAs, leading to false warnings during process teardown. The vulnerability has been resolved in the Linux kernel.
AI Analysis
Technical Summary
The Linux kernel had a vulnerability in mm/memory where the unmap path incorrectly tested whether a folio was anonymous using vma_is_anonymous(), which does not always align with folio_test_anon(). This mismatch could cause spurious warnings when unmapping device-private or exclusive pages, especially in cases where folios are part of private file-backed mappings. The issue was fixed by correcting the condition checks to properly handle these cases, eliminating the false warnings during process teardown.
Potential Impact
The impact is limited to spurious kernel warnings during process teardown related to memory unmapping of device-private or exclusive pages. There is no indication of security compromise, data leakage, or system instability beyond these warnings. No known exploits exist in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the condition checks causing the spurious warnings. Users should update to the fixed kernel versions once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory or Linux kernel mailing lists for the official fix and update guidance.
In the Linux kernel, the following vulnerability has been resolved: mm/memory: fix spurious warning when unmapping device-private/exclusive pages… (CVE-2026-64131)
Description
A vulnerability in the Linux kernel's memory management subsystem caused spurious warnings when unmapping device-private or exclusive pages. This issue arises from an incorrect condition check between anonymous folios and anonymous VMAs, leading to false warnings during process teardown. The vulnerability has been resolved in the Linux kernel.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel had a vulnerability in mm/memory where the unmap path incorrectly tested whether a folio was anonymous using vma_is_anonymous(), which does not always align with folio_test_anon(). This mismatch could cause spurious warnings when unmapping device-private or exclusive pages, especially in cases where folios are part of private file-backed mappings. The issue was fixed by correcting the condition checks to properly handle these cases, eliminating the false warnings during process teardown.
Potential Impact
The impact is limited to spurious kernel warnings during process teardown related to memory unmapping of device-private or exclusive pages. There is no indication of security compromise, data leakage, or system instability beyond these warnings. No known exploits exist in the wild.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to correct the condition checks causing the spurious warnings. Users should update to the fixed kernel versions once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory or Linux kernel mailing lists for the official fix and update guidance.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-2qhr-9xff-qp48
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64131"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a5d27a82a4a8d598912b236
Added to database: 07/19/2026, 19:38:16 UTC
Last enriched: 07/19/2026, 19:46:49 UTC
Last updated: 07/20/2026, 17:26:47 UTC
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.