CVE-2026-80856 — fuse: fix invalidate lock leak on setattr writeback failure
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+1
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < 8f14906ce9103ab8f2f1ebda45935a0d61b9d763≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < 03cfeeb135428fa83f0791d3f8f94d9298cae695≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < 92588d187ba4697a322e7aefe5d9e538a87d1cd2≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < ea9fea370b8de4ffd72e0ef89550415c15637787≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < dd278d954c0e96a9cbd3cc491e07b8267d25f8d5≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < e8457ebfd77a46e8d1210e8888ea914ad064558e≥ 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and < 9afeca0d569c9fc89d758fe7a9339d1e8afb1546 and 1 moreversion 5.10 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 27, 2026 · 12 reading(s) · max 0.17%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 19, 2026 – Oct 19, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
10 on the record
- git.kernel.org/stable/c/e8457ebfd77a46e8d1210e8888ea914ad064558e
- git.kernel.org/stable/c/03cfeeb135428fa83f0791d3f8f94d9298cae695
- git.kernel.org/stable/c/92588d187ba4697a322e7aefe5d9e538a87d1cd2
- nvd.nist.gov/vuln/detail/CVE-2026-80856
- git.kernel.org/stable/c/dd278d954c0e96a9cbd3cc491e07b8267d25f8d5
- git.kernel.org/stable/c/9afeca0d569c9fc89d758fe7a9339d1e8afb1546
- git.kernel.org/stable/c/8f14906ce9103ab8f2f1ebda45935a0d61b9d763
- git.kernel.org/stable/c/1758730d9eaa3c06cf415c3446d9f6eed9ed3eed
- github.com/advisories/GHSA-4jx3-fh7f-pxhw
- git.kernel.org/stable/c/ea9fea370b8de4ffd72e0ef89550415c15637787
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 7h
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 7h
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 7h
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 7h
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 7h
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 7h
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-80856 is "fuse: fix invalidate lock leak on setattr writeback failure", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.17% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.