CVE-2026-74319
Last modified
CVE-2026-74319 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock waiting for ticket during data relocation When performing data relocation on a zoned filesystem, BTRFS can deadlock in handle_reserve_tickets(). The relocation process is waiting on a space reservation ticket that can never be fulfilled, because the relocation itself is the operation responsible for freeing up that space. Fix this by introducing a new flush state, BTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk allocation during zoned relocation. EPSS estimates a 0.15% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: btrfs: zoned: fix deadlock waiting for ticket during data relocation When performing data relocation on a zoned filesystem, BTRFS can deadlock in handle_reserve_tickets(). The relocation process is waiting on a space reservation ticket that can never be fulfilled, because the relocation itself is the operation responsible for freeing up that space. Fix this by introducing a new flush state, BTRFS_RESERVE_FLUSH_ZONED_RELOCATION, specifically for data chunk allocation during zoned relocation. Like BTRFS_RESERVE_FLUSH_FREE_SPACE_INODE, this state uses priority_reclaim_data_space() instead of the normal flushing path, which avoids re-entering the relocation code and breaking the deadlock cycle. In btrfs_alloc_data_chunk_ondemand(), select this new flush state when the inode belongs to a data relocation root on a zoned filesystem.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= e2a7fd22378f6500bcf979edc71e6837271eacfd, < f84dbbaa988e1344634a20ddf6c7d51a99f12477; >= e2a7fd22378f6500bcf979edc71e6837271eacfd, < 814c3b4ea357297c507158bceb07bcdc5fbe9808 |
| Linux | Linux | 7.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-74319?
How severe is CVE-2026-74319?
How do I fix CVE-2026-74319?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-74313In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74314In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74315In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-74316In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-74317In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-74318In the Linux kernel, the following vulnerability has been re…
- CVE-2026-7432A race condition in Ivanti Secure Access Client before 22.8R…7
- CVE-2026-74320In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74321In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-74322In the Linux kernel, the following vulnerability has been re…
- CVE-2026-74323In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-74324In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-74319?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
