CVE-2026-64294
Last modified
CVE-2026-64294 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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.. EPSS estimates a 0.20% chance of exploitation in the next 30 days.
Description
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.12, < 6.6.145 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.96 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.39 | — |
| Linux | Linux Kernel | >= 6.19, < 7.1.4 | — |
| Linux | Linux Kernel | 7.2 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64294?
How severe is CVE-2026-64294?
How do I fix CVE-2026-64294?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64289In the Linux kernel, the following vulnerability has been re…
- CVE-2026-6429When asked to both use a `.netrc` file for credentials and t…5.3
- CVE-2026-64290In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64291In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64292In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64293In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64295In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64296In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64297In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64298In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64299In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-64300In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-64294?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
