CVE-2026-74595

In the Linux kernel, the following vulnerability has been resolved:<br /> <br /> fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy()<br /> <br /> fscrypt_ioctl_set_policy() calls inode_owner_or_capable() with<br /> &amp;nop_mnt_idmap before allowing an encryption policy to be set, instead<br /> of the idmap of the mount the ioctl was issued on.<br /> <br /> fscrypt is used by filesystems that support idmapped mounts (e.g. ext4,<br /> f2fs), so on such a mount this compares the caller&amp;#39;s fsuid against the<br /> unmapped on-disk owner rather than the mapped owner: the actual owner<br /> can be wrongly denied with -EACCES and an unrelated caller wrongly<br /> allowed. Use file_mnt_idmap(filp) instead.