Linux Kernel up to 7.1.10/7.2.0 XFS xfs_trans_roll deadlock

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00- |
Summary
A vulnerability labeled as critical has been found in Linux Kernel up to 7.1.10/7.2.0. This vulnerability affects the function xfs_trans_roll of the component XFS. The manipulation results in deadlock.
This vulnerability is known as CVE-2026-80804. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability was found in Linux Kernel up to 7.1.10/7.2.0. It has been classified as critical. Affected is the function xfs_trans_roll of the component XFS. The manipulation with an unknown input leads to a deadlock vulnerability. CWE is classifying the issue as CWE-833. The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock. This is going to have an impact on availability. CVE summarizes:
In the Linux kernel, the following vulnerability has been resolved: xfs: restore nofs context unconditionally in xfs_trans_roll When __xfs_trans_commit() fails in xfs_trans_roll(), the NOFS context is cleared but only restored in the success path. This leaves the error path without nofs protection, causing a circular lock dependency between xfs_nondir_ilock_class and fs_reclaim: CPU0 CPU1 ---- ---- lock(&xfs_nondir_ilock_class); lock(fs_reclaim); lock(&xfs_nondir_ilock_class); lock(fs_reclaim); Fix this by moving xfs_trans_set_context() before the error check so that nofs context is always restored on the new transaction.
The advisory is shared for download at git.kernel.org. This vulnerability is traded as CVE-2026-80804 since 08/26/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are known technical details, but no exploit is available.
Upgrading to version 7.1.11, 7.2.1 or 7.3-rc1 eliminates this vulnerability. Applying the patch b09198cf90ccf296970b774beea1c1ddb260f94c/4d00a39c676274f4071b467e630565ac1e3ae0f2 is able to eliminate this problem.
Once again VulDB remains the best source for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: DeadlockCWE: CWE-833 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 7.1.11/7.2.1/7.3-rc1
Patch: b09198cf90ccf296970b774beea1c1ddb260f94c/4d00a39c676274f4071b467e630565ac1e3ae0f2
Timeline
08/26/2026 CVE reserved09/04/2026 Advisory disclosed
09/04/2026 VulDB entry created
09/04/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-80804 (🔒)
GCVE (CVE): GCVE-0-2026-80804
GCVE (VulDB): GCVE-100-398940
Entry
Created: 09/04/2026 18:26Changes: 09/04/2026 18:26 (59)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.