Linux Kernel up to 7.2.2 FUSE fuse_open locking

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.41-

Summaryinfo

A vulnerability labeled as critical has been found in Linux Kernel up to 7.2.2. The affected element is the function fuse_open of the component FUSE. Such manipulation leads to locking. This vulnerability is traded as CVE-2026-80855. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Linux Kernel up to 7.2.2. Affected by this issue is the function fuse_open of the component FUSE. The manipulation with an unknown input leads to a locking vulnerability. Using CWE to declare the problem leads to CWE-667. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. Impacted is availability. CVE summarizes:

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.

The advisory is available at git.kernel.org. This vulnerability is handled as CVE-2026-80855 since 08/26/2026. The exploitation is known to be easy. The attack may be launched remotely. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/04/2026).

Upgrading to version 5.15.220, 6.1.187, 6.6.156, 6.12.108, 6.18.49, 7.1.13, 7.2.3 or 7.3-rc1 eliminates this vulnerability. Applying the patch 1b04d80a27d317064cce2307472f5bef9975bc50/a61524da59a2f5ac9c8de23ff98b30da769ab144/dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010/7288c279ddbd654a06c82118c1a3f5570c1807f0/776e85fda752f9a15e0f82dec42ecacd12a9bd94/1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da/e981474d7bf1457da12404e169ea147d2c8ecea7/a927f1867e61b78f39f9da0bbba3c98c2ca151fe is able to eliminate this problem.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Locking
CWE: CWE-667
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Yes

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.15.220/6.1.187/6.6.156/6.12.108/6.18.49/7.1.13/7.2.3/7.3-rc1
Patch: 1b04d80a27d317064cce2307472f5bef9975bc50/a61524da59a2f5ac9c8de23ff98b30da769ab144/dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010/7288c279ddbd654a06c82118c1a3f5570c1807f0/776e85fda752f9a15e0f82dec42ecacd12a9bd94/1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da/e981474d7bf1457da12404e169ea147d2c8ecea7/a927f1867e61b78f39f9da0bbba3c98c2ca151fe

Timelineinfo

08/26/2026 CVE reserved
09/04/2026 +9 days Advisory disclosed
09/04/2026 +0 days VulDB entry created
09/04/2026 +0 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2026-80855 (🔒)
GCVE (CVE): GCVE-0-2026-80855
GCVE (VulDB): GCVE-100-398954

Entryinfo

Created: 09/04/2026 18:32
Changes: 09/04/2026 18:32 (59)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!