CVE-2022-48734
published 2024-06-20CVE-2022-48734: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between quota disable and qgroup rescan worker Quota disable ioctl…
PriorityP419medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.18%
7.5th percentile
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock between quota disable and qgroup rescan worker
Quota disable ioctl starts a transaction before waiting for the qgroup
rescan worker completes. However, this wait can be infinite and results
in deadlock because of circular dependency among the quota disable
ioctl, the qgroup rescan worker and the other task with transaction such
as block group relocation task.
The deadlock happens with the steps following:
1) Task A calls ioctl to disable quota. It starts a transaction and
waits for qgroup rescan worker completes.
2) Task B such as block group relocation task starts a transaction and
joins to the transaction that task A started. Then task B commits to
the transaction. In this commit, task B waits for a commit by task A.
3) Task C as the qgroup rescan worker starts its job and starts a
transaction. In this transaction start, task C waits for completion
of the transaction that task A started and task B committed.
This deadlock was found with fstests test case btrfs/115 and a zoned
null_blk device. The test case enables and disables quota, and the
block group reclaim was triggered during the quota disable by chance.
The deadlock was also observed by running quota enable and disable in
parallel with 'btrfs balance' command on regular null_blk devices.
An example report of the deadlock:
[372.469894] INFO: task kworker/u16:6:103 blocked for more than 122 seconds.
[372.479944] Not tainted 5.16.0-rc8 #7
[372.485067] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[372.493898] task:kworker/u16:6 state:D stack: 0 pid: 103 ppid: 2 flags:0x00004000
[372.503285] Workqueue: btrfs-qgroup-rescan btrfs_work_helper [btrfs]
[372.510782] Call Trace:
[372.514092]
[372.521684] __schedule+0xb56/0x4850
[372.530104] ? io_schedule_timeout+0x190/0x190
[372.538842] ? lockdep_hardirqs_on+0x7e/0x100
[372.547092] ? _raw_spin_unlock_irqrestore+0x3e/0x60
[372.555591] schedule+0xe0
Affected
15 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.16.10-1 (bookworm) | linux 5.16.10-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 967ef5131e42d6e3bb216c44161d893048a49957 < 26b3901d20bf9da2c6a00cb1fb48932166f80a45 | 26b3901d20bf9da2c6a00cb1fb48932166f80a45 |
| linux | linux | >= 967ef5131e42d6e3bb216c44161d893048a49957 < 32747e01436aac8ef93fe85b5b523b4f3b52f040 | 32747e01436aac8ef93fe85b5b523b4f3b52f040 |
| linux | linux | >= 967ef5131e42d6e3bb216c44161d893048a49957 < 89d4cca583fc9594ee7d1a0bc986886d6fb587e6 | 89d4cca583fc9594ee7d1a0bc986886d6fb587e6 |
| linux | linux | >= 967ef5131e42d6e3bb216c44161d893048a49957 < 31198e58c09e21d4f65c49d2361f76b87aca4c3f | 31198e58c09e21d4f65c49d2361f76b87aca4c3f |
| linux | linux | >= 967ef5131e42d6e3bb216c44161d893048a49957 < e804861bd4e69cc5fe1053eedcb024982dde8e48 | e804861bd4e69cc5fe1053eedcb024982dde8e48 |
| linux | linux_kernel | < 5.4.178 | 5.4.178 |
| linux | linux_kernel | >= 0 < 5.10.103-1 | 5.10.103-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 0 < 5.16.10-1 | 5.16.10-1 |
| linux | linux_kernel | >= 5.11 < 5.15.22 | 5.15.22 |
| linux | linux_kernel | >= 5.16 < 5.16.8 | 5.16.8 |
| linux | linux_kernel | >= 5.5 < 5.10.99 | 5.10.99 |
CVSS provenance
nvdv3.15.5MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
osv5.5MEDIUM
vendor_debian5.5MEDIUM
vendor_redhat5.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2022-48734: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between quota disable and qgroup rescan worker Quota disable i
osv·2024-06-20·CVSS 5.5
CVE-2022-48734 [MEDIUM] CVE-2022-48734: In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between quota disable and qgroup rescan worker Quota disable i
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between quota disable and qgroup rescan worker Quota disable ioctl starts a transaction before waiting for the qgroup rescan worker completes. However, this wait can be infinite and results in deadlock because of circular dependency among the quota disable ioctl, the qgroup rescan worker and the other task with transaction such as block group relocation task. The deadlock happens with the steps following: 1) Task A calls ioctl to disable quota. It starts a transaction and waits for qgroup rescan worker completes. 2) Task B such as block group relocation task starts a transaction and joins to the transaction that task A started. Then task B commits to the transaction. In this commit, task B waits for a c
GHSA
GHSA-wrfr-rmr8-j7gx: In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock between quota disable and qgroup rescan worker
Quota disable
ghsa_unreviewed·2024-06-20
CVE-2022-48734 [MEDIUM] CWE-667 GHSA-wrfr-rmr8-j7gx: In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock between quota disable and qgroup rescan worker
Quota disable
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock between quota disable and qgroup rescan worker
Quota disable ioctl starts a transaction before waiting for the qgroup
rescan worker completes. However, this wait can be infinite and results
in deadlock because of circular dependency among the quota disable
ioctl, the qgroup rescan worker and the other task with transaction such
as block group relocation task.
The deadlock happens with the steps following:
1) Task A calls ioctl to disable quota. It starts a transaction and
waits for qgroup rescan worker completes.
2) Task B such as block group relocation task starts a transaction and
joins to the transaction that task A started. Then task B commits to
the transaction. In this commit, task B waits for
Red Hat
kernel: btrfs: fix deadlock between quota disable and qgroup rescan worker
vendor_redhat·2024-06-20·CVSS 5.5
CVE-2022-48734 [MEDIUM] CWE-833 kernel: btrfs: fix deadlock between quota disable and qgroup rescan worker
kernel: btrfs: fix deadlock between quota disable and qgroup rescan worker
In the Linux kernel, the following vulnerability has been resolved:
btrfs: fix deadlock between quota disable and qgroup rescan worker
Quota disable ioctl starts a transaction before waiting for the qgroup
rescan worker completes. However, this wait can be infinite and results
in deadlock because of circular dependency among the quota disable
ioctl, the qgroup rescan worker and the other task with transaction such
as block group relocation task.
The deadlock happens with the steps following:
1) Task A calls ioctl to disable quota. It starts a transaction and
waits for qgroup rescan worker completes.
2) Task B such as block group relocation task starts a transaction and
joins to the transaction that task A started.
Debian
CVE-2022-48734: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
vendor_debian·2022·CVSS 5.5
CVE-2022-48734 [MEDIUM] CVE-2022-48734: linux - In the Linux kernel, the following vulnerability has been resolved: btrfs: fix ...
In the Linux kernel, the following vulnerability has been resolved: btrfs: fix deadlock between quota disable and qgroup rescan worker Quota disable ioctl starts a transaction before waiting for the qgroup rescan worker completes. However, this wait can be infinite and results in deadlock because of circular dependency among the quota disable ioctl, the qgroup rescan worker and the other task with transaction such as block group relocation task. The deadlock happens with the steps following: 1) Task A calls ioctl to disable quota. It starts a transaction and waits for qgroup rescan worker completes. 2) Task B such as block group relocation task starts a transaction and joins to the transaction that task A started. Then task B commits to the transaction. In this commit, task B waits for a c
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://git.kernel.org/stable/c/26b3901d20bf9da2c6a00cb1fb48932166f80a45https://git.kernel.org/stable/c/31198e58c09e21d4f65c49d2361f76b87aca4c3fhttps://git.kernel.org/stable/c/32747e01436aac8ef93fe85b5b523b4f3b52f040https://git.kernel.org/stable/c/89d4cca583fc9594ee7d1a0bc986886d6fb587e6https://git.kernel.org/stable/c/e804861bd4e69cc5fe1053eedcb024982dde8e48https://git.kernel.org/stable/c/26b3901d20bf9da2c6a00cb1fb48932166f80a45https://git.kernel.org/stable/c/31198e58c09e21d4f65c49d2361f76b87aca4c3fhttps://git.kernel.org/stable/c/32747e01436aac8ef93fe85b5b523b4f3b52f040https://git.kernel.org/stable/c/89d4cca583fc9594ee7d1a0bc986886d6fb587e6https://git.kernel.org/stable/c/e804861bd4e69cc5fe1053eedcb024982dde8e48
2024-06-20
Published