Strix
63.5K

CVE-2026-80856

Unknown

Last modified

CVE-2026-80856 is a vulnerability of currently unknown severity. 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.

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.

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < 8f14906ce9103ab8f2f1ebda45935a0d61b9d763; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < 03cfeeb135428fa83f0791d3f8f94d9298cae695; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < 92588d187ba4697a322e7aefe5d9e538a87d1cd2; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < ea9fea370b8de4ffd72e0ef89550415c15637787; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < dd278d954c0e96a9cbd3cc491e07b8267d25f8d5; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < e8457ebfd77a46e8d1210e8888ea914ad064558e; >= 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f, < 9afeca0d569c9fc89d758fe7a9339d1e8afb1546
LinuxLinux5.10

References

Timeline

Published
Last Modified
Status
Received

Frequently Asked Questions

What is CVE-2026-80856?
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.
How severe is CVE-2026-80856?
Severity scoring for CVE-2026-80856 is pending analysis.
How do I fix CVE-2026-80856?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-80856?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST