Skip to main content
VulnerabilityPublished Updated

CVE-2026-68149: Linux kernel · fs: preserve ACL_DONT_CACHE state in forget_cached_acl()

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 8.4 High · fixed in ca03a7984a34f48085fd013e0d2cf4e6420b4acf : patch Linux kernel soon.

Data as of 26 Oct 2026, 14:18 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in ca03a7984a34f48085fd013e0d2cf4e6420b4acf, b98fad81f1202b0eb26aacf3ff4cc7a21ed3b5bf, a019b074903b3ad0a9726087efd0e8291452023b +2
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ facd61053cff100973921d4d45d47cf53c747ec6, < ca03a7984a34f48085fd013e0d2cf4e6420b4acf
Fixed in
  • ca03a7984a34f48085fd013e0d2cf4e6420b4acf
LinuxLinuxAffected
  • ≥ facd61053cff100973921d4d45d47cf53c747ec6, < b98fad81f1202b0eb26aacf3ff4cc7a21ed3b5bf
Fixed in
  • b98fad81f1202b0eb26aacf3ff4cc7a21ed3b5bf
LinuxLinuxAffected
  • ≥ facd61053cff100973921d4d45d47cf53c747ec6, < a019b074903b3ad0a9726087efd0e8291452023b
Fixed in
  • a019b074903b3ad0a9726087efd0e8291452023b
LinuxLinuxAffected
  • ≥ facd61053cff100973921d4d45d47cf53c747ec6, < 834ddf899484a2f23129080e8773bc04f4691d07
Fixed in
  • 834ddf899484a2f23129080e8773bc04f4691d07
LinuxLinuxAffected
  • ≥ facd61053cff100973921d4d45d47cf53c747ec6, < 4b9a5458d02e214ef2b384124ca626e3e381d778
Fixed in
  • 4b9a5458d02e214ef2b384124ca626e3e381d778
LinuxLinuxAffected
  • =6.2
Fixed in–

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.

References

Community reviews

Loading reviews…