CVE-2026-64294
CVE CVE-2026-64294EUVD EUVD-2026-49006Published 2026-07-25T08:49:32.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux patch: 6.6.145; patch: 7.2-rc3; 9caccd41541a6f7d6279928d9f971f6642c361af <5c942ad7df75925ee166e7f0fb36892d8dde376b; patch: 6.18.39; 9caccd41541a6f7d6279928d9f971f6642c361af <04ba248d02d9eaa3d9077b00a6134caa75fa3e90; 5.12; 9caccd41541a6f7d6279928d9f971f6642c361af <8344bdf0629457e532797b42d9d2bbf2a2900bbf; patch: 7.1.4; patch: 0; 9caccd41541a6f7d6279928d9f971f6642c361af <e187bc02f8fa4226d62814592cf064ee4557c470; patch: 6.12.96; 9caccd41541a6f7d6279928d9f971f6642c361af <744b23aa430d52f5c8e4dbff7d71496d6643bed2
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.