CVE-2026-80856: fuse: fix invalidate lock leak on setattr writeback failure
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Fixed version: Linux Linux 03cfeeb135428fa83f0791d3f8f94d9298cae695, 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed, 8f14906ce9103ab8f2f1ebda45935a0d61b9d763; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 03cfeeb135428fa83f0791d3f8f94d9298cae695, 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed, 8f14906ce9103ab8f2f1ebda45935a0d61b9d763; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 4, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.10affected
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 92faaee1b108c6e4b07730d20896a6593a85f675affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 8f14906ce9103ab8f2f1ebda45935a0d61b9d763affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 03cfeeb135428fa83f0791d3f8f94d9298cae695affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 92588d187ba4697a322e7aefe5d9e538a87d1cd2affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before ea9fea370b8de4ffd72e0ef89550415c15637787affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 1758730d9eaa3c06cf415c3446d9f6eed9ed3eedaffected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before dd278d954c0e96a9cbd3cc491e07b8267d25f8d5affected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before e8457ebfd77a46e8d1210e8888ea914ad064558eaffected · git
- 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f and later · before 9afeca0d569c9fc89d758fe7a9339d1e8afb1546affected · git
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.1.13-1 | 7.1.13-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-80854Sep 4, 2026 · usb: gadget: f_tcm: keep port count until LUN teardown completes0Monitor
- ← EarlierCVE-2026-80855Sep 4, 2026 · fuse: fix invalidate lock leak on open O_TRUNC DAX failure0Monitor
- Later →CVE-2026-80857Sep 4, 2026 · fuse: wait for FR_FINISHED on abort_on_kill to prevent use-after-free0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 03cfeeb135428fa83f0791d3f8f94d9298cae695 | Vendor (CNA) |
| Linux Linux | 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed | Vendor (CNA) |
| Linux Linux | 8f14906ce9103ab8f2f1ebda45935a0d61b9d763 | Vendor (CNA) |
| Linux Linux | 92588d187ba4697a322e7aefe5d9e538a87d1cd2 | Vendor (CNA) |
| Linux Linux | 92faaee1b108c6e4b07730d20896a6593a85f675 | Vendor (CNA) |
| Linux Linux | 9afeca0d569c9fc89d758fe7a9339d1e8afb1546 | Vendor (CNA) |
| Linux Linux | dd278d954c0e96a9cbd3cc491e07b8267d25f8d5 | Vendor (CNA) |
| Linux Linux | e8457ebfd77a46e8d1210e8888ea914ad064558e | Vendor (CNA) |
| Linux Linux | ea9fea370b8de4ffd72e0ef89550415c15637787 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (8 more)Show less
- git.kernel.org/stable/c/1758730d9eaa3c06cf415c3446d9f6eed9ed3eed
- git.kernel.org/stable/c/8f14906ce9103ab8f2f1ebda45935a0d61b9d763
- git.kernel.org/stable/c/92588d187ba4697a322e7aefe5d9e538a87d1cd2
- git.kernel.org/stable/c/92faaee1b108c6e4b07730d20896a6593a85f675
- git.kernel.org/stable/c/9afeca0d569c9fc89d758fe7a9339d1e8afb1546
- git.kernel.org/stable/c/dd278d954c0e96a9cbd3cc491e07b8267d25f8d5
- git.kernel.org/stable/c/e8457ebfd77a46e8d1210e8888ea914ad064558e
- git.kernel.org/stable/c/ea9fea370b8de4ffd72e0ef89550415c15637787
Vendor advisories and official records. Exploit/PoC links are deliberately left out.