In the Linux kernel, the following vulnerability has been resolved: mm: do file ownership checks with the proper mount idmap Ever since idmapped… (CVE-2026-64294)
A vulnerability in the Linux kernel related to file ownership checks in the memory management subsystem was resolved. The issue involved incorrect handling of inode ownership checks with idmapped mounts, causing owner_or_capable() checks to fail due to improper mount idmap usage. This could lead to unexpected permission check failures in certain edge cases, such as when a file's ownership is translated by an idmap but the check uses a default idmap that ignores this translation. The fix introduced a new function to correctly handle ownership semantics with idmaps.
AI Analysis
Technical Summary
The Linux kernel vulnerability CVE-2026-64294 concerns improper file ownership checks in the memory management code, specifically in mincore() and madvise(MADV_PAGEOUT) system calls. Since the introduction of idmapped mounts, inode ownership checks were performed against a nop_mnt_idmap, which ignores the file's actual mount idmap. This caused owner_or_capable() checks to fail when the file ownership was translated by an idmap, leading to permission check inconsistencies. The fix involved creating a new file_owner_or_capable() function that correctly applies the mount idmap during ownership checks, replacing the previous incorrect usage.
Potential Impact
The vulnerability could cause permission checks to fail unexpectedly in certain scenarios involving idmapped mounts, potentially leading to incorrect access control decisions. However, in typical cases such as mincore() and madvise(MADV_PAGEOUT), the impact is usually benign because other permission checks use the correct idmap. There is no indication of direct exploitation or privilege escalation in the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by introducing a new function that correctly applies mount idmaps during file ownership checks. Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the official patch accordingly.
In the Linux kernel, the following vulnerability has been resolved: mm: do file ownership checks with the proper mount idmap Ever since idmapped… (CVE-2026-64294)
Description
A vulnerability in the Linux kernel related to file ownership checks in the memory management subsystem was resolved. The issue involved incorrect handling of inode ownership checks with idmapped mounts, causing owner_or_capable() checks to fail due to improper mount idmap usage. This could lead to unexpected permission check failures in certain edge cases, such as when a file's ownership is translated by an idmap but the check uses a default idmap that ignores this translation. The fix introduced a new function to correctly handle ownership semantics with idmaps.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel vulnerability CVE-2026-64294 concerns improper file ownership checks in the memory management code, specifically in mincore() and madvise(MADV_PAGEOUT) system calls. Since the introduction of idmapped mounts, inode ownership checks were performed against a nop_mnt_idmap, which ignores the file's actual mount idmap. This caused owner_or_capable() checks to fail when the file ownership was translated by an idmap, leading to permission check inconsistencies. The fix involved creating a new file_owner_or_capable() function that correctly applies the mount idmap during ownership checks, replacing the previous incorrect usage.
Potential Impact
The vulnerability could cause permission checks to fail unexpectedly in certain scenarios involving idmapped mounts, potentially leading to incorrect access control decisions. However, in typical cases such as mincore() and madvise(MADV_PAGEOUT), the impact is usually benign because other permission checks use the correct idmap. There is no indication of direct exploitation or privilege escalation in the provided data.
Mitigation Recommendations
A fix has been implemented in the Linux kernel to address this issue by introducing a new function that correctly applies mount idmaps during file ownership checks. Users should update to a Linux kernel version that includes this fix. Patch status is not explicitly confirmed in the provided data; therefore, check the official Linux kernel advisories or vendor updates for the exact fixed versions and apply the official patch accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-rgg7-9234-2h22
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64294"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a65420e9c2644c7f8086309
Added to database: 07/25/2026, 23:09:02 UTC
Last enriched: 07/25/2026, 23:39:00 UTC
Last updated: 07/26/2026, 04:47:38 UTC
Views: 5
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.