CVE-2026-80856
Received Received - Intake

fuse: Lock Leak in setattr Writeback Failure

Vulnerability report for CVE-2026-80856, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: fuse: fix invalidate lock leak on setattr writeback failure fuse_do_setattr() takes filemap_invalidate_lock() for a DAX truncate (fault_blocked = true) and releases it at the out:/error: labels. But when a writeback flush is also needed, a write_inode_now() failure returns directly and leaks the lock, so any later fault or truncate on the file stalls on the stale rwsem. For example, truncate(2) on a setuid file reaches fuse_do_setattr() with both ATTR_SIZE and ATTR_MODE set: truncate(2) └─ do_truncate() β”œβ”€ dentry_needs_remove_privs() # S_ISUID └─ notify_change() # KILL_SUID -> ATTR_MODE └─ fuse_setattr() # no killpriv: β”‚ # ia_valid |= ATTR_MODE └─ fuse_do_setattr() β”œβ”€ filemap_invalidate_lock() # IS_DAX && is_truncate └─ write_inode_now() # is_wb && ATTR_MODE └─ if (err) # e.g. daemon -> -EIO return err # <- lock leaked Fix this by adding an unlock label that releases the lock before returning the error, and use it for the fuse_dax_break_layouts() failure path as well.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-25
AI Q&A
2026-09-04
EPSS Evaluated
2026-09-23
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves a lock leak in the FUSE (Filesystem in Userspace) subsystem. When a file operation like truncate fails during writeback, the filemap_invalidate_lock is not properly released, causing subsequent file operations to stall.

Detection Guidance

This vulnerability is specific to the Linux kernel's FUSE (Filesystem in Userspace) implementation and requires kernel-level inspection. Detection involves checking kernel logs for fuse-related errors or stalls during file operations. No direct network detection commands are applicable. Review kernel logs with 'dmesg | grep fuse' or 'journalctl -k | grep fuse' for lock-related errors or stalls.

Impact Analysis

This could lead to system hangs or unresponsiveness when accessing files managed by FUSE filesystems, especially during operations like truncate or fault handling. Users may experience delays or complete stalls in file operations.

Compliance Impact

This vulnerability is a Linux kernel flaw related to a lock leak during file operations. It does not directly impact compliance with standards like GDPR or HIPAA, as those focus on data protection, privacy, and security controls rather than kernel-level file system issues.

Mitigation Strategies

Update your Linux kernel to the latest patched version to resolve the fuse invalidate lock leak issue. Monitor for kernel crashes or hangs related to file operations, especially on DAX-enabled filesystems.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80856. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart