CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX 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 1b04d80a27d317064cce2307472f5bef9975bc50, 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da, 5.10.273; 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 1b04d80a27d317064cce2307472f5bef9975bc50, 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da, 5.10.273; 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 open O_TRUNC DAX failure fuse_open() takes filemap_invalidate_lock() for a DAX truncate (dax_truncate = true) and releases it before the out_inode_unlock label. But when fuse_dax_break_layouts() fails, the goto out_inode_unlock skips the unlock and leaks the rwsem, so any later fault or truncate on the file stalls on the stale lock. fuse_dax_break_layouts() can fail with -ERESTARTSYS when a signal interrupts the wait for busy DAX pages to drain: open("file", O_RDWR | O_TRUNC) └─ fuse_open() ├─ filemap_invalidate_lock() # dax_truncate └─ fuse_dax_break_layouts() └─ dax_break_layout() └─ wait_page_idle() # TASK_INTERRUPTIBLE └─ fuse_wait_dax_page() # unlock, schedule, re-lock └─ signal → -ERESTARTSYS goto out_inode_unlock # <- lock leaked Fix this by moving filemap_invalidate_unlock() below the label so that all error paths release the lock, and rename the label to out_unlock as it now covers more than just the inode lock.
- 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
- b57e150ac2eac791d5d187923b73dc2dafaf67fa, 1fdbbe246daf348adaa0739463384b16ceba1fc0, 6.0affected
- 81775ab858b4236c52c5da7e25cec6e49dd91b46 and later · before 69a294e561c10909688bcb25456535dcd1818e1aaffected · git
- d58366aab86854217b81679d1a9dcd54a2edfc2a and later · before 1b04d80a27d317064cce2307472f5bef9975bc50affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before a61524da59a2f5ac9c8de23ff98b30da769ab144affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before 7288c279ddbd654a06c82118c1a3f5570c1807f0affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before 776e85fda752f9a15e0f82dec42ecacd12a9bd94affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74daaffected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before e981474d7bf1457da12404e169ea147d2c8ecea7affected · git
- 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and later · before a927f1867e61b78f39f9da0bbba3c98c2ca151feaffected · 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-80853Sep 4, 2026 · KVM: SEV: Allocate full pages for {DE,EN}CRYPT ops on SNP-enabled hosts0Monitor
- ← EarlierCVE-2026-80854Sep 4, 2026 · usb: gadget: f_tcm: keep port count until LUN teardown completes0Monitor
- Later →CVE-2026-80856Sep 4, 2026 · fuse: fix invalidate lock leak on setattr writeback failure0Monitor
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 | 1b04d80a27d317064cce2307472f5bef9975bc50 | Vendor (CNA) |
| Linux Linux | 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da | Vendor (CNA) |
| Linux Linux | 5.10.273 | Vendor (CNA) |
| Linux Linux | 5.15.220 | Vendor (CNA) |
| Linux Linux | 5.19 | Vendor (CNA) |
| Linux Linux | 5.20 | Vendor (CNA) |
| Linux Linux | 69a294e561c10909688bcb25456535dcd1818e1a | Vendor (CNA) |
| Linux Linux | 7288c279ddbd654a06c82118c1a3f5570c1807f0 | Vendor (CNA) |
| Linux Linux | 776e85fda752f9a15e0f82dec42ecacd12a9bd94 | Vendor (CNA) |
| Linux Linux | a61524da59a2f5ac9c8de23ff98b30da769ab144 | Vendor (CNA) |
| Linux Linux | a927f1867e61b78f39f9da0bbba3c98c2ca151fe | Vendor (CNA) |
| Linux Linux | dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010 | Vendor (CNA) |
| Linux Linux | e981474d7bf1457da12404e169ea147d2c8ecea7 | Vendor (CNA) |
| 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/1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da
- git.kernel.org/stable/c/69a294e561c10909688bcb25456535dcd1818e1a
- git.kernel.org/stable/c/7288c279ddbd654a06c82118c1a3f5570c1807f0
- git.kernel.org/stable/c/776e85fda752f9a15e0f82dec42ecacd12a9bd94
- git.kernel.org/stable/c/a61524da59a2f5ac9c8de23ff98b30da769ab144
- git.kernel.org/stable/c/a927f1867e61b78f39f9da0bbba3c98c2ca151fe
- git.kernel.org/stable/c/dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010
- git.kernel.org/stable/c/e981474d7bf1457da12404e169ea147d2c8ecea7
Vendor advisories and official records. Exploit/PoC links are deliberately left out.