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-64294mm: do file ownership checks with the proper mount idmap

Description

In the Linux kernel, the following vulnerability has been resolved: mm: do file ownership checks with the proper mount idmap Ever since idmapped mounts were introduced, inode ownership checks (for side-channel protection) in mincore() and madvise(MADV_PAGEOUT) were done against the nop_mnt_idmap, which completely ignores the file's mount's idmap. This results in odd edgecases like: 1) mount/bind-mount with an idmap userA:userB:1 2) userB runs an owner_or_capable() check on file that is owned by userA on-disk/in-memory, but owned by userB after idmap translation 3) owner_or_capable() mysteriously fails as the correct idmap wasn't supplied In the case of mincore/madvise MADV_PAGEOUT, this is usually benign, because file_permission(file, MAY_WRITE) will probably succeed, as it uses the proper idmap internally, but it does not need to be the case on e.g a 0444 file where even the owner itself doesn't have permissions to write to it. Since this is clearly not trivial to get right, introduce a file_owner_or_capable() that can carry the correct semantics, and switch the various users in mm to it. The issue was found by manual code inspection & an off-list discussion with Jan Kara.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 3 months 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-64294, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (14 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < 7368bec565bac3e536cd43579dbde1e715e6ba61
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < b2f3d94ea310bea9d36d53e9d9b3f45e86c1d893
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < 744b23aa430d52f5c8e4dbff7d71496d6643bed2
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < 8344bdf0629457e532797b42d9d2bbf2a2900bbf
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < 5c942ad7df75925ee166e7f0fb36892d8dde376b
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < 04ba248d02d9eaa3d9077b00a6134caa75fa3e90
    • affected 9caccd41541a6f7d6279928d9f971f6642c361af – < e187bc02f8fa4226d62814592cf064ee4557c470
  • Linux · Linux

    • affected 5.12
    • unaffected < 5.12
    • unaffected 5.15.217 – ≤ 5.15.*
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 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-64294 badge
[![CVE-2026-64294](https://cveledger.app/badge/CVE-2026-64294.svg)](https://cveledger.app/cve/CVE-2026-64294)

Record last updated .