CVE-2026-74595

Unknown

Last modified

CVE-2026-74595 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 174633a468817a49bd474bcfc9067c84e54efe68; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 0baeb730044981f5ec5fb7d62a3763835ea606f6; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 33b7e810ce09955aa02f3b632455cf5e7ac990a9; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 6a67c460b12315033268dce597546984fe5739e7; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 653e888a24c87b8bbeab44d7e558a1c1a3641088; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < 98516ba8b817f34e86bdd7a5b7a383cff75c3ddf; >= 14f3db5542e62bcf6fe088a09760ac52d55306c5, < cf6c993c0feca7984797e634deba3c80342e199a
LinuxLinux5.12

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is 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.
How severe is CVE-2026-74595?
Severity scoring for CVE-2026-74595 is pending analysis.
How do I fix CVE-2026-74595?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-74595?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST