PULSE
FEED
ransombarracuda reclama a EVINOKS · TR · Technologyransomqilin reclama a Danser · US · Otherransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***upransombarracuda reclama a EVINOKS · TR · Technologyransomqilin reclama a Danser · US · Otherransomvexy ransomware reclama a System Soft · BG · Technologyransomvexy ransomware reclama a JHAMF Group · BDransomemperador reclama a Punta Shopping · BR · Retail & E-Commerceransomnightspire reclama a **F*A *.Aransompayload reclama a Straze Garden Center · Retail & E-Commerceransompayload reclama a Kraft Lernen · DE · Educationransompayload reclama a SALEG (Sachsen-Anhaltische Landesentwicklungsgesellschaft mbH) · DE · Government & Defenseransomrhysida reclama a Phoenix Charter Academy · US · Educationransomauditteam reclama a Pe***CT · NLransomauditteam reclama a jl***om · SGransomauditteam reclama a hn***rgransomauditteam reclama a ro***up
← All CVEs
CVE WatchOct 16, 2026

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_p

CVSS

7.8

High

EPSS

0.1%

p1

KEV

—

Exploit Today

0

0-100

Published: Aug 22, 2026 · Last modified: Oct 16, 2026

EPSS · 30d
0.1%EPSS · 30 days0.1%
2026-10-032026-10-30
Technical 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.

Official references
Related CVEs

No related CVEs by CWE or product.