Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2026-68149

fs: preserve ACL_DONT_CACHE state in forget_cached_acl()

High8.4EPSS 0.14%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: fs: preserve ACL_DONT_CACHE state in forget_cached_acl() The ACL_DONT_CACHE state is meant to be a constant state for the inode for filesystems that want to opt out of posix acl caching. Commit facd61053cff1 ("fuse: fixes after adapting to new posix acl api") used this facility to opt out of posix acl caching for fuse inodes with fuse server that does not negotiate FUSE_POSIX_ACL (fc->posix_acl). The commit also takes care to gate the forget_all_cached_acls() call in fuse_set_acl() on fc->posix_acl because there is no need for it, but there are other placed in fuse code which call forget_all_cached_acls() unconditional to fc->posix_acl and those cause the loss of the ACL_DONT_CACHE state. This is not only a functional bug. Properly timed, a get_acl() from this fuse filesystem can return a stale cached value, as was observed in tests, because set_acl() does not invalidate the unintentional acl cache. We could fix this in fuse, but it actually makes no sense for the vfs helper forget_cached_acl() to invalidate the ACL_DONT_CACHE state, so let it not do that to fix fuse and future users of ACL_DONT_CACHE.

Scores

CVSS scores of CVE-2026-68149, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
NVDNVD · Received3.1High8.4CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
EPSS (exploitation in 30 days)
0.14% · top 97% of all CVEs (6 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 8.4.

Weakness

Affected products

  • Linux · Linux

    • affected facd61053cff100973921d4d45d47cf53c747ec6 – < b98fad81f1202b0eb26aacf3ff4cc7a21ed3b5bf
    • affected facd61053cff100973921d4d45d47cf53c747ec6 – < 834ddf899484a2f23129080e8773bc04f4691d07
    • affected facd61053cff100973921d4d45d47cf53c747ec6 – < a019b074903b3ad0a9726087efd0e8291452023b
    • affected facd61053cff100973921d4d45d47cf53c747ec6 – < ca03a7984a34f48085fd013e0d2cf4e6420b4acf
    • affected facd61053cff100973921d4d45d47cf53c747ec6 – < 4b9a5458d02e214ef2b384124ca626e3e381d778
  • Linux · Linux

    • affected 6.2
    • unaffected < 6.2
    • unaffected 6.6.148 – ≤ 6.6.*
    • unaffected 6.12.101 – ≤ 6.12.*
    • unaffected 6.18.42 – ≤ 6.18.*
    • unaffected 7.1.6 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References (5)

Sources

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

Badge for a README or a ticket

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

Record last updated .