CVE-2026-74595
N/AIn 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.
No known exploitation, public exploit, or elevated probability at this time. Track for changes.
Exploitation likelihood
—EPSS not yet scored
Impact if exploited
—CVSS · not scored
- No impact metrics
Proof of concept & exploit code
- github-search Search GitHub for public PoC repos
Test against your own equipment
curl -s https://vulnpedia.com/cve/CVE-2026-74595/poc.jsonMachine-readable PoC index for this CVE (for automation).Listed for defensive triage, patch verification, and authorized testing on systems you own. Machine-readable: /cve/CVE-2026-74595/poc.json
References
Technical & other
- https://git.kernel.org/stable/c/33b7e810ce09955aa02f3b632455cf5e7ac990a9
- https://git.kernel.org/stable/c/6a67c460b12315033268dce597546984fe5739e7
- https://git.kernel.org/stable/c/653e888a24c87b8bbeab44d7e558a1c1a3641088
- https://git.kernel.org/stable/c/98516ba8b817f34e86bdd7a5b7a383cff75c3ddf
- https://git.kernel.org/stable/c/cf6c993c0feca7984797e634deba3c80342e199a