CyberRota Analysis
AI-GeneratedThe vulnerability affects the Linux kernel's fscrypt functionality, specifically in the `fscrypt_ioctl_set_policy()` function, which improperly checks the owner of files on idmapped mounts. This flaw can lead to unauthorized access, allowing an unrelated user to set encryption policies while potentially denying access to the actual file owner. Organizations using Linux with filesystems that support idmapped mounts, such as ext4 and f2fs, should prioritize addressing this issue to mitigate potential security risks.
Original NVD Description
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.