CVE-2023-53730
published 2025-10-22CVE-2023-53730: In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost…
PriorityP421low5.5
EPSS
0.19%
8.9th percentile
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled
when unlock. DEADLOCK might happen if we have held other locks and disabled
IRQ before invoking it.
Fix it by using spin_lock_irqsave() instead, which can keep IRQ state
consistent with before when unlock.
WARNING: inconsistent lock state
5.10.0-02758-g8e5f91fd772f #26 Not tainted
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes:
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390
{IN-HARDIRQ-W} state was registered at:
__lock_acquire+0x3d7/0x1070
lock_acquire+0x197/0x4a0
__raw_spin_lock_irqsave
_raw_spin_lock_irqsave+0x3b/0x60
bfq_idle_slice_timer_body
bfq_idle_slice_timer+0x53/0x1d0
__run_hrtimer+0x477/0xa70
__hrtimer_run_queues+0x1c6/0x2d0
hrtimer_interrupt+0x302/0x9e0
local_apic_timer_interrupt
__sysvec_apic_timer_interrupt+0xfd/0x420
run_sysvec_on_irqstack_cond
sysvec_apic_timer_interrupt+0x46/0xa0
asm_sysvec_apic_timer_interrupt+0x12/0x20
irq event stamp: 837522
hardirqs last enabled at (837521): [] __raw_spin_unlock_irqrestore
hardirqs last enabled at (837521): [] _raw_spin_unlock_irqrestore+0x3d/0x40
hardirqs last disabled at (837522): [] __raw_spin_lock_irq
hardirqs last disabled at (837522): [] _raw_spin_lock_irq+0x43/0x50
softirqs last enabled at (835852): [] __do_softirq+0x558/0x8ec
softirqs last disabled at (835845): [] asm_call_irq_on_stack+0xf/0x20
other info that might help us debug this:
Possible unsafe locking scenario:
CPU0
----
lock(&bfqd->lock);
lock(&bfqd->lock);
*** DEADLOCK ***
3 locks held by kworker/2:3/388:
#0: ffff888107af0f38 ((wq_completion)kthrotld){+.+.}-{0:0}, at: process_one_work+0x742/0x13f0
#1: ffff8881176bfdd8 ((work_completion)(&td->dispatch_work)){+.+.}-{0:0}, at: process_one_work+0x777
Affected
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.52-1 (bookworm) | linux 6.1.52-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < 8563b58a4360e648ce18f0e98a75a4be51667431 | 8563b58a4360e648ce18f0e98a75a4be51667431 |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < eb120c0aff5ceab9c9c46b87f302465bbf2bbaed | eb120c0aff5ceab9c9c46b87f302465bbf2bbaed |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < 8ceeb3fc86a83700bb1585c189006080a47e8506 | 8ceeb3fc86a83700bb1585c189006080a47e8506 |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < 9279a1b74ad98039d5d44d26b9e7a9cfe655b6d3 | 9279a1b74ad98039d5d44d26b9e7a9cfe655b6d3 |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < 3376c4fe2db4aea2dc721a27a999c41fdb45b54f | 3376c4fe2db4aea2dc721a27a999c41fdb45b54f |
| linux | linux | >= b0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4 < 8d211554679d0b23702bd32ba04aeac0c1c4f660 | 8d211554679d0b23702bd32ba04aeac0c1c4f660 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.52-1 | 6.1.52-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 0 < 6.4.4-1 | 6.4.4-1 |
| linux | linux_kernel | >= 5.10.0 < 5.10.188 | 5.10.188 |
| linux | linux_kernel | >= 5.11.0 < 5.15.121 | 5.15.121 |
| linux | linux_kernel | >= 5.16.0 < 6.1.39 | 6.1.39 |
| linux | linux_kernel | >= 6.2.0 < 6.3.13 | 6.3.13 |
| linux | linux_kernel | >= 6.4.0 < 6.4.4 | 6.4.4 |
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.
Red Hat
kernel: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
vendor_redhat·2025-10-22·CVSS 5.5
CVE-2023-53730 [LOW] CWE-833 kernel: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
kernel: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled
when unlock. DEADLOCK might happen if we have held other locks and disabled
IRQ before invoking it.
Fix it by using spin_lock_irqsave() instead, which can keep IRQ state
consistent with before when unlock.
WARNING: inconsistent lock state
5.10.0-02758-g8e5f91fd772f #26 Not tainted
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes:
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390
{IN-
Debian
CVE-2023-53730: linux - In the Linux kernel, the following vulnerability has been resolved: blk-iocost:...
vendor_debian·2023
CVE-2023-53730 CVE-2023-53730: linux - In the Linux kernel, the following vulnerability has been resolved: blk-iocost:...
In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before invoking it. Fix it by using spin_lock_irqsave() instead, which can keep IRQ state consistent with before when unlock. ================================ WARNING: inconsistent lock state 5.10.0-02758-g8e5f91fd772f #26 Not tainted -------------------------------- inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390 {IN-HARDIRQ
VulDB
Linux Kernel up to 6.4.3 adjust_inuse_and_calc_cost deadlock (Nessus ID 319448 / WID-SEC-2025-2394)
vuldb·2026-06-08
CVE-2023-53730 [CRITICAL] Linux Kernel up to 6.4.3 adjust_inuse_and_calc_cost deadlock (Nessus ID 319448 / WID-SEC-2025-2394)
A vulnerability labeled as critical has been found in Linux Kernel up to 5.10.187/5.15.120/6.1.38/6.3.12/6.4.3. Affected by this issue is the function adjust_inuse_and_calc_cost. Executing a manipulation can lead to deadlock.
The identification of this vulnerability is CVE-2023-53730. The attack needs to be done within the local network. There is no exploit available.
The affected component should be upgraded.
OSV
CVE-2023-53730: In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_c
osv·2025-10-22
CVE-2023-53730 CVE-2023-53730: In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_c
In the Linux kernel, the following vulnerability has been resolved: blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled when unlock. DEADLOCK might happen if we have held other locks and disabled IRQ before invoking it. Fix it by using spin_lock_irqsave() instead, which can keep IRQ state consistent with before when unlock. ================================ WARNING: inconsistent lock state 5.10.0-02758-g8e5f91fd772f #26 Not tainted -------------------------------- inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage. kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390 {IN-HARDIRQ
OSV
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
osv·2025-10-22
CVE-2023-53730 blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled
when unlock. DEADLOCK might happen if we have held other locks and disabled
IRQ before invoking it.
Fix it by using spin_lock_irqsave() instead, which can keep IRQ state
consistent with before when unlock.
WARNING: inconsistent lock state
5.10.0-02758-g8e5f91fd772f #26 Not tainted
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes:
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390
{IN-HARD
GHSA
GHSA-qcg4-xxf6-m8j4: In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and
ghsa_unreviewed·2025-10-22
CVE-2023-53730 GHSA-qcg4-xxf6-m8j4: In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
adjust_inuse_and_calc_cost() use spin_lock_irq() and IRQ will be enabled
when unlock. DEADLOCK might happen if we have held other locks and disabled
IRQ before invoking it.
Fix it by using spin_lock_irqsave() instead, which can keep IRQ state
consistent with before when unlock.
WARNING: inconsistent lock state
5.10.0-02758-g8e5f91fd772f #26 Not tainted
inconsistent {IN-HARDIRQ-W} -> {HARDIRQ-ON-W} usage.
kworker/2:3/388 [HC0[0]:SC0[0]:HE0:SE1] takes:
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spin_lock_irq
ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfq_bio_merge+0x141/0x390
{IN-HARDIRQ-W} state was registered at:
__lock_acquire+0x3d7/0x1070
lock_
No detection rules found.
No public exploits indexed.
https://git.kernel.org/stable/c/3376c4fe2db4aea2dc721a27a999c41fdb45b54fhttps://git.kernel.org/stable/c/8563b58a4360e648ce18f0e98a75a4be51667431https://git.kernel.org/stable/c/8ceeb3fc86a83700bb1585c189006080a47e8506https://git.kernel.org/stable/c/8d211554679d0b23702bd32ba04aeac0c1c4f660https://git.kernel.org/stable/c/9279a1b74ad98039d5d44d26b9e7a9cfe655b6d3https://git.kernel.org/stable/c/eb120c0aff5ceab9c9c46b87f302465bbf2bbaed
2025-10-22
Published