CVE-2026-80856
CVE CVE-2026-80856EUVD EUVD-2026-71306Published 2026-09-04T15:55:09.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <e8457ebfd77a46e8d1210e8888ea914ad064558e; patch: 6.18.49; patch: 6.6.156; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <ea9fea370b8de4ffd72e0ef89550415c15637787; patch: 6.12.108; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <dd278d954c0e96a9cbd3cc491e07b8267d25f8d5; patch: 0; patch: 7.2.3; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <9afeca0d569c9fc89d758fe7a9339d1e8afb1546; patch: 6.1.187; 5.10; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <03cfeeb135428fa83f0791d3f8f94d9298cae695; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <92588d187ba4697a322e7aefe5d9e538a87d1cd2; patch: 5.15.220; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <1758730d9eaa3c06cf415c3446d9f6eed9ed3eed; 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f <8f14906ce9103ab8f2f1ebda45935a0d61b9d763; patch: 7.1.13; patch: 7.3-rc1
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.