CVSS
Вероятност да бъде експлоатирана в следващите 30 дни (EPSS)
Атакува се
Време до експлоатация
- Експлоатация: няма данни за експлоатация
- Атаката не може да се автоматизира
Описание
Оригинално описание
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock in wait_current_trans() due to ignored transaction type When wait_current_trans() is called during start_transaction(), it currently waits for a blocked transaction without considering whether the given transaction type actually needs to wait for that particular transaction state. The btrfs_blocked_trans_types[] array already defines which transaction types should wait for which transaction states, but this check was missing in wait_current_trans(). This can lead to a deadlock scenario involving two transactions and pending ordered extents: 1. Transaction A is in TRANS_STATE_COMMIT_DOING state 2. A worker processing an ordered extent calls start_transaction() with TRANS_JOIN 3. join_transaction() returns -EBUSY because Transaction A is in TRANS_STATE_COMMIT_DOING 4. Transaction A moves to TRANS_STATE_UNBLOCKED and completes 5. A new Transaction B is created (TRANS_STATE_RUNNING) 6. The ordered extent from step 2 is added to Transaction B's pending ordered extents 7. Transaction B immediately starts commit by another task and enters TRANS_STATE_COMMIT_START 8. The worker finally reaches wait_current_trans(), sees Transaction B in TRANS_STATE_COMMIT_START (a blocked state), and waits unconditionally 9. However, TRANS_JOIN should NOT wait for TRANS_STATE_COMMIT_START according to btrfs_blocked_trans_types[] 10. Transaction B is waiting for pending ordered extents to complete 11. Deadlock: Transaction B waits for ordered extent, ordered extent waits for Transaction B This can be illustrated by the following call stacks: CPU0 CPU1 btrfs_finish_ordered_io() start_transaction(TRANS_JOIN) join_transaction() # -EBUSY (Transactio
Засегнати продукти
- Linux Linux: 4a9d8bdee368de78ace8b36da4eb2186afea162d преди e563f59395981fcd69d130761290929806e728d6; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди dc84036c173cff6a432d9ab926298850b1d2a659; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди d7b04b40ac8e6d814e35202a0e1568809b818295; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди 99da896614d17e8a84aeb2b2d464ac046cc8633d; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди 8b0bb145d3bc264360f525c9717653be3522e528; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди 9ac63333d600732a56b35ee1fa46836da671eb50; 4a9d8bdee368de78ace8b36da4eb2186afea162d преди 5037b342825df7094a4906d1e2a9674baab50cb2
- Linux Linux: 3.11; преди 3.11; 5.10.249 до 5.10.*; 5.15.199 до 5.15.*; 6.1.162 до 6.1.*; 6.6.122 до 6.6.*; 6.12.67 до 6.12.*; 6.18.7 до 6.18.*; от 6.19 нататък
Вид слабост
История
- 4 февруари 2026 Публикувано
Други уязвимости в Linux Linux
Първоизточници
- https://www.cve.org/CVERecord?id=CVE-2025-71194
- https://nvd.nist.gov/vuln/detail/CVE-2025-71194
- https://git.kernel.org/stable/c/e563f59395981fcd69d130761290929806e728d6
- https://git.kernel.org/stable/c/dc84036c173cff6a432d9ab926298850b1d2a659
- https://git.kernel.org/stable/c/d7b04b40ac8e6d814e35202a0e1568809b818295
- https://git.kernel.org/stable/c/99da896614d17e8a84aeb2b2d464ac046cc8633d
- https://git.kernel.org/stable/c/8b0bb145d3bc264360f525c9717653be3522e528
- https://git.kernel.org/stable/c/9ac63333d600732a56b35ee1fa46836da671eb50
- https://git.kernel.org/stable/c/5037b342825df7094a4906d1e2a9674baab50cb2