| Release Date: | 2026-09-04 | |
| Impact: | Moderate | What is this? |
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.
See more information about CVE-2026-80856 from MITRE CVE dictionary and NIST NVD
NOTE: The following CVSS metrics and score provided are preliminary and subject to review.
| Base Score: | 3.3 |
| Vector String: | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L |
| Version: | 3.1 |
| Attack Vector: | Local |
| Attack Complexity: | Low |
| Privileges Required: | Low |
| User Interaction: | None |
| Scope: | Unchanged |
| Confidentiality Impact: | None |
| Integrity Impact: | None |
| Availability Impact: | Low |
| Platform | Errata | Release Date |
| Oracle Linux version 8 (kernel-uek) | ELSA-2026-500377 | 2026-10-07 |
| Oracle Linux version 9 (kernel-uek) | ELSA-2026-500374 | 2026-10-07 |
| Oracle Linux version 9 (kernel-uek) | ELSA-2026-500377 | 2026-10-07 |
This page is generated automatically and has not been checked for errors or omissions. For clarification or corrections: