CVE-2026-64294

published 25 Jul 2026 · updated 14 Nov 2026

mm: do file ownership checks with the proper mount idmap

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 6.6.145, Kernel 6.18.39, Kernel 7.1.4 and 10 more.

In the Linux kernel, the following vulnerability has been resolved: mm: do file ownership checks with the proper mount idmap Ever since idmapped mounts were introduced, inode ownership checks (for side-channel protection) in mincore() and madvise(MADV_PAGEOUT) were done against the nop_mnt_idmap, which completely ignores the file's mount's idmap. This results in odd edgecases like: 1) mount/bind-mount with an idmap userA:userB:1 2) userB runs an owner_or_capable() check on file that is owned by userA on-disk/in-memory, but owned by userB after idmap translation 3) owner_or_capable() mysteriously fails as the correct idmap wasn't supplied In the case of mincore/madvise MADV_PAGEOUT, this is usually benign, because file_permission(file, MAY_WRITE) will probably succeed, as it uses the proper idmap internally, but it does not need to be the case on e.g a 0444 file where even the owner itself doesn't have permissions to write to it. Since this is clearly not trivial to get right, introduce a file_owner_or_capable() that can carry the correct semantics, and switch the various users in mm to it. The issue was found by manual code inspection & an off-list discussion with Jan Kara.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=5.12 <6.6.145, >=6.13 <6.18.39, >=6.19 <7.1.4, >=6.7 <6.12.96, =7.2, >=9caccd41541a6f7d6279928d9f971f6642c361af <5c942ad7df75925ee166e7f0fb36892d8dde376b, >=9caccd41541a6f7d6279928d9f971f6642c361af <7368bec565bac3e536cd43579dbde1e715e6ba61, >=9caccd41541a6f7d6279928d9f971f6642c361af <744b23aa430d52f5c8e4dbff7d71496d6643bed2, >=9caccd41541a6f7d6279928d9f971f6642c361af <8344bdf0629457e532797b42d9d2bbf2a2900bbf, >=9caccd41541a6f7d6279928d9f971f6642c361af <b2f3d94ea310bea9d36d53e9d9b3f45e86c1d893, >=9caccd41541a6f7d6279928d9f971f6642c361af <e187bc02f8fa4226d62814592cf064ee4557c470, =5.12, >=9caccd41541a6f7d6279928d9f971f6642c361af <04ba248d02d9eaa3d9077b00a6134caa75fa3e906.6.145, 6.18.39, 7.1.4, 6.12.96, 5c942ad7df75925ee166e7f0fb36892d8dde376b, 7368bec565bac3e536cd43579dbde1e715e6ba61, 744b23aa430d52f5c8e4dbff7d71496d6643bed2, 8344bdf0629457e532797b42d9d2bbf2a2900bbf, b2f3d94ea310bea9d36d53e9d9b3f45e86c1d893, e187bc02f8fa4226d62814592cf064ee4557c470, 04ba248d02d9eaa3d9077b00a6134caa75fa3e90
linux-kernel: Kernel>=5.12.0 <5.15.217, >=5.16.0 <6.1.184, >=6.13.0 <6.18.39, >=6.19.0 <7.1.4, >=6.2.0 <6.6.145, >=6.7.0 <6.12.965.15.217, 6.1.184, 6.18.39, 7.1.4, 6.6.145, 6.12.96

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64294 severity on Zeptric[![CVE-2026-64294](https://zeptric.io/badge/cve/CVE-2026-64294.svg)](https://zeptric.io/cve/CVE-2026-64294)