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-80855fuse: fix invalidate lock leak on open O_TRUNC DAX failure

Description

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.

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 (15 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 81775ab858b4236c52c5da7e25cec6e49dd91b46 – < 69a294e561c10909688bcb25456535dcd1818e1a
    • affected d58366aab86854217b81679d1a9dcd54a2edfc2a – < 1b04d80a27d317064cce2307472f5bef9975bc50
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < a61524da59a2f5ac9c8de23ff98b30da769ab144
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < 7288c279ddbd654a06c82118c1a3f5570c1807f0
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < 776e85fda752f9a15e0f82dec42ecacd12a9bd94
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < e981474d7bf1457da12404e169ea147d2c8ecea7
    • affected 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b – < a927f1867e61b78f39f9da0bbba3c98c2ca151fe
    • affected b57e150ac2eac791d5d187923b73dc2dafaf67fa
    • affected 1fdbbe246daf348adaa0739463384b16ceba1fc0
    • affected 5.10.179 – < 5.10.273
    • affected 5.15.109 – < 5.15.220
    • affected 5.18.18 – < 5.19
    • affected 5.19.2 – < 5.20
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • 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-80855 badge
[![CVE-2026-80855](https://cveledger.app/badge/CVE-2026-80855.svg)](https://cveledger.app/cve/CVE-2026-80855)

Record last updated .