CVE-2026-74595
In the Linux kernel, the following vulnerability has been resolved: fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() fscrypt_ioctl_set_policy() calls inode_owner_or_capable() with &nop_mnt_idmap before allowing an encryption policy to be set, instead of the idmap of the mount the ioctl was issued on. fscrypt is used by filesystems that support idmapped mounts (e.g. ext4, f2fs), so on such a mount this compares the caller's fsuid against the unmapped on-disk owner rather than the mapped owner: the actual owner can be wrongly denied with -EACCES and an unrelated caller wrongly allowed. Use file_mnt_idmap(filp) instead.
Affected versions
Linux kernel versions
5.12
and later are affected. Fixed in
6.6.152,
6.12.104,
6.18.45,
7.1.9,
7.2
and their respective stable series.
References
5 totalFrequently asked questions
-
What is CVE-2026-74595?
CVE-2026-74595 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 5.12 onward and has been patched in 6.6.152, 6.12.104, 6.18.45 and others. CVE-2026-74595 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-74595?
Yes. CVE-2026-74595 has been patched. Fixed versions include 6.6.152, 6.12.104, 6.18.45 and others. If you are running Linux kernel 5.12 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-74595 actively exploited?
No. CVE-2026-74595 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.