Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By Linux

  2. · 7 days later

    Published

  3. · 55 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-74595, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.09% · top 99% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 174633a468817a49bd474bcfc9067c84e54efe68
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 0baeb730044981f5ec5fb7d62a3763835ea606f6
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 33b7e810ce09955aa02f3b632455cf5e7ac990a9
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 6a67c460b12315033268dce597546984fe5739e7
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 653e888a24c87b8bbeab44d7e558a1c1a3641088
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < 98516ba8b817f34e86bdd7a5b7a383cff75c3ddf
    • affected 14f3db5542e62bcf6fe088a09760ac52d55306c5 – < cf6c993c0feca7984797e634deba3c80342e199a
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.45 – ≤ 6.18.*
    • unaffected 7.1.9 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74595 badge
[![CVE-2026-74595](https://cveledger.app/badge/CVE-2026-74595.svg)](https://cveledger.app/cve/CVE-2026-74595)

Record last updated .