CVE-2026-80856: Linux kernel · fuse: fix invalidate lock leak on setattr writeback failure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in ea9fea370b8de4ffd72e0ef89550415c15637787 : update Linux kernel when convenient.
Data as of 30 Oct 2026, 13:06 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
Thin evidence
One scorer or none- Patch
- Available – fixed in ea9fea370b8de4ffd72e0ef89550415c15637787, e8457ebfd77a46e8d1210e8888ea914ad064558e, dd278d954c0e96a9cbd3cc491e07b8267d25f8d5 +6
Exploitation evidence
Disclosed: evidence found.
CVE published 4 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 30 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users and administrators should update to a fixed kernel version containing the patches identified by the listed commit hashes to resolve the lock leak issue. No additional mitigation steps are indicated.
Description
A vulnerability in the Linux kernel's FUSE subsystem causes a lock leak when a setattr writeback operation fails. Specifically, fuse_do_setattr() may leak the filemap_invalidate_lock if write_inode_now() returns an error during a writeback flush, leading to potential stalls on subsequent file operations such as truncate. This issue has been fixed by ensuring the lock is properly released on error paths.
References
- git.kernel.org/stable/c/92faaee1b108c6e4b07730d20896a6593a85f675 (opens in a new tab)
- git.kernel.org/stable/c/8f14906ce9103ab8f2f1ebda45935a0d61b9d763 (opens in a new tab)
- git.kernel.org/stable/c/03cfeeb135428fa83f0791d3f8f94d9298cae695 (opens in a new tab)
- git.kernel.org/stable/c/92588d187ba4697a322e7aefe5d9e538a87d1cd2 (opens in a new tab)
- git.kernel.org/stable/c/ea9fea370b8de4ffd72e0ef89550415c15637787 (opens in a new tab)
- git.kernel.org/stable/c/1758730d9eaa3c06cf415c3446d9f6eed9ed3eed (opens in a new tab)
- git.kernel.org/stable/c/dd278d954c0e96a9cbd3cc491e07b8267d25f8d5 (opens in a new tab)
- git.kernel.org/stable/c/e8457ebfd77a46e8d1210e8888ea914ad064558e (opens in a new tab)
- git.kernel.org/stable/c/9afeca0d569c9fc89d758fe7a9339d1e8afb1546 (opens in a new tab)