fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy() (CVE-2026-74595) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-74595

fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy()

Answer in brief

CVE-2026-74595 records a Unknown severity vulnerability in fscrypt: use the mount idmap for the owner check in fscrypt_ioctl_set_policy(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 22, 2026Updated Aug 22, 2026Source checked Aug 22, 2026First seen by HOL Aug 22, 2026Material review Aug 22, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=14f3db5542e62bcf6fe088a09760ac52d55306c5 <33b7e810ce09955aa02f3b632455cf5e7ac990a9 \|\| >=14f3db5542e62bcf6fe088a09760ac52d55306c5 <6a67c460b12315033268dce597546984fe5739e7 \|\| >=14f3db5542e62bcf6fe088a09760ac52d55306c5 <653e888a24c87b8bbeab44d7e558a1c1a3641088 \|\| >=14f3db5542e62bcf6fe088a09760ac52d55306c5 <98516ba8b817f34e86bdd7a5b7a383cff75c3ddf \|\| >=14f3db5542e62bcf6fe088a09760ac52d55306c5 <cf6c993c0feca7984797e634deba3c80342e199a	33b7e810ce09955aa02f3b632455cf5e7ac990a9, 6a67c460b12315033268dce597546984fe5739e7, 653e888a24c87b8bbeab44d7e558a1c1a3641088, 98516ba8b817f34e86bdd7a5b7a383cff75c3ddf, cf6c993c0feca7984797e634deba3c80342e199a
Linux/Linuxgeneric	5.12	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 33b7e810ce09955aa02f3b632455cf5e7ac990a9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Aug 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Aug 22, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.