Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-80856fuse: fix invalidate lock leak on setattr writeback failure

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 56 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.18% · top 92% of all CVEs (16 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 92faaee1b108c6e4b07730d20896a6593a85f675
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 8f14906ce9103ab8f2f1ebda45935a0d61b9d763
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 03cfeeb135428fa83f0791d3f8f94d9298cae695
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 92588d187ba4697a322e7aefe5d9e538a87d1cd2
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < ea9fea370b8de4ffd72e0ef89550415c15637787
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 1758730d9eaa3c06cf415c3446d9f6eed9ed3eed
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < dd278d954c0e96a9cbd3cc491e07b8267d25f8d5
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < e8457ebfd77a46e8d1210e8888ea914ad064558e
    • affected 6ae330cad6ef22ab8347ea9e0707dc56a7c7363f – < 9afeca0d569c9fc89d758fe7a9339d1e8afb1546
  • Linux · Linux

    • affected 5.10
    • unaffected < 5.10
    • unaffected 5.10.273 – ≤ 5.10.*
    • unaffected 5.15.220 – ≤ 5.15.*
    • unaffected 6.1.187 – ≤ 6.1.*
    • unaffected 6.6.156 – ≤ 6.6.*
    • unaffected 6.12.108 – ≤ 6.12.*
    • unaffected 6.18.49 – ≤ 6.18.*
    • unaffected 7.1.13 – ≤ 7.1.*
    • unaffected 7.2.3 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-80856 badge
[![CVE-2026-80856](https://cveledger.app/badge/CVE-2026-80856.svg)](https://cveledger.app/cve/CVE-2026-80856)

Record last updated .