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 during the unmapping of device-private or exclusive pages. This issue arises from an incorrect assumption in the code about the relationship between anonymous folios and anonymous VMAs, leading to warnings during process teardown. The vulnerability does not impact confidentiality or integrity but can cause availability issues due to these warnings.
AI Analysis
Technical Summary
The Linux kernel had a flaw in the mm/memory code where the unmap path incorrectly tested whether a folio was anonymous by using vma_is_anonymous(), which does not always align with folio_test_anon(). This mismatch can occur when a folio is part of a private file-backed mapping, causing spurious warnings during device-private/exclusive page unmapping. The issue was fixed by correcting the condition checks to properly handle these cases, preventing the warnings during process teardown.
Potential Impact
This vulnerability does not affect confidentiality or integrity but can cause availability issues by generating spurious kernel warnings during process teardown. These warnings may indicate instability or unexpected behavior in memory management but do not represent a direct security compromise.
Mitigation Recommendations
A fix for this issue has been implemented in the Linux kernel. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation 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 during the unmapping of device-private or exclusive pages. This issue arises from an incorrect assumption in the code about the relationship between anonymous folios and anonymous VMAs, leading to warnings during process teardown. The vulnerability does not impact confidentiality or integrity but can cause availability issues due to these warnings.
CVSS v3.1
Score 5.5medium
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel had a flaw in the mm/memory code where the unmap path incorrectly tested whether a folio was anonymous by using vma_is_anonymous(), which does not always align with folio_test_anon(). This mismatch can occur when a folio is part of a private file-backed mapping, causing spurious warnings during device-private/exclusive page unmapping. The issue was fixed by correcting the condition checks to properly handle these cases, preventing the warnings during process teardown.
Potential Impact
This vulnerability does not affect confidentiality or integrity but can cause availability issues by generating spurious kernel warnings during process teardown. These warnings may indicate instability or unexpected behavior in memory management but do not represent a direct security compromise.
Mitigation Recommendations
A fix for this issue has been implemented in the Linux kernel. Users should update to the fixed kernel version once available. Patch status is not explicitly confirmed in the provided data; therefore, check the vendor advisory for current remediation 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: 08/13/2026, 19:16:29 UTC
Last updated: 09/03/2026, 10:52:10 UTC
Views: 55
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.