CVE-2023-53730
- Source
- https://cve.org/CVERecord?id=CVE-2023-53730
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2023-53730.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2023-53730
- Downstream
- Related
- Published
- 2025-10-22T13:23:58.419Z
- Modified
- 2026-01-30T02:39:18.079479Z
- Summary
- blk-iocost: use spin_lock_irqsave in adjust_inuse_and_calc_cost
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
blk-iocost: use spinlockirqsave in adjustinuseandcalccost
adjustinuseandcalccost() use spinlockirq() 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 spinlockirqsave() 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: spinlockirq ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfqbiomerge+0x141/0x390 {IN-HARDIRQ-W} state was registered at: __lockacquire+0x3d7/0x1070 lockacquire+0x197/0x4a0 __rawspinlockirqsave rawspinlockirqsave+0x3b/0x60 bfqidleslicetimerbody bfqidleslicetimer+0x53/0x1d0 __run_hrtimer+0x477/0xa70 __hrtimerrunqueues+0x1c6/0x2d0 hrtimerinterrupt+0x302/0x9e0 localapictimerinterrupt __sysvecapictimerinterrupt+0xfd/0x420 runsysveconirqstackcond sysvecapictimerinterrupt+0x46/0xa0 asmsysvecapictimerinterrupt+0x12/0x20 irq event stamp: 837522 hardirqs last enabled at (837521): [<ffffffff84b9419d>] __rawspinunlock_irqrestore hardirqs last enabled at (837521): [<ffffffff84b9419d>] rawspinunlockirqrestore+0x3d/0x40 hardirqs last disabled at (837522): [<ffffffff84b93fa3>] __rawspinlock_irq hardirqs last disabled at (837522): [<ffffffff84b93fa3>] rawspinlockirq+0x43/0x50 softirqs last enabled at (835852): [<ffffffff84e00558>] _dosoftirq+0x558/0x8ec softirqs last disabled at (835845): [<ffffffff84c010ff>] asmcallirqonstack+0xf/0x20
other info that might help us debug this: Possible unsafe locking scenario:
CPU0 ---- lock(&bfqd->lock); <Interrupt> lock(&bfqd->lock);*** DEADLOCK ***
3 locks held by kworker/2:3/388: #0: ffff888107af0f38 ((wqcompletion)kthrotld){+.+.}-{0:0}, at: processonework+0x742/0x13f0 #1: ffff8881176bfdd8 ((workcompletion)(&td->dispatchwork)){+.+.}-{0:0}, at: processonework+0x777/0x13f0 #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: spinlockirq #2: ffff888118c00c28 (&bfqd->lock){?.-.}-{2:2}, at: bfqbio_merge+0x141/0x390
stack backtrace: CPU: 2 PID: 388 Comm: kworker/2:3 Not tainted 5.10.0-02758-g8e5f91fd772f #26 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 Workqueue: kthrotld blkthrotldispatchworkfn Call Trace: __dumpstack lib/dumpstack.c:77 [inline] dump_stack+0x107/0x167 printusagebug validstate marklockirq.cold+0x32/0x3a marklock+0x693/0xbc0 markheldlocks+0x9e/0xe0 __tracehardirqsoncaller lockdephardirqsonprepare.part.0+0x151/0x360 tracehardirqson+0x5b/0x180 __rawspinunlockirq rawspinunlockirq+0x24/0x40 spinunlockirq adjustinuseandcalccost+0x4fb/0x970 iocrqos_merge+0x277/0x740 __rqqosmerge+0x62/0xb0 rqqosmerge bioattemptbackmerge+0x12c/0x4a0 blkmqschedtrymerge+0x1b6/0x4d0 bfqbio_merge+0x24a/0x390 __blkmqschedbiomerge+0xa6/0x460 blkmqschedbiomerge blkmqsubmit_bio+0x2e7/0x1ee0 __submitbionoacctmq+0x175/0x3b0 submitbionoacct+0x1fb/0x270 blkthrotldispatchworkfn+0x1ef/0x2b0 processonework+0x83e/0x13f0 processscheduledworks workerthread+0x7e3/0xd80 kthread+0x353/0x470 retfromfork+0x1f/0x30
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53730.json" }- References
-
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- https://git.kernel.org/stable/c/3376c4fe2db4aea2dc721a27a999c41fdb45b54f
- https://git.kernel.org/stable/c/8563b58a4360e648ce18f0e98a75a4be51667431
- https://git.kernel.org/stable/c/8ceeb3fc86a83700bb1585c189006080a47e8506
- https://git.kernel.org/stable/c/8d211554679d0b23702bd32ba04aeac0c1c4f660
- https://git.kernel.org/stable/c/9279a1b74ad98039d5d44d26b9e7a9cfe655b6d3
- https://git.kernel.org/stable/c/eb120c0aff5ceab9c9c46b87f302465bbf2bbaed
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2023/53xxx/CVE-2023-53730.json
- https://nvd.nist.gov/vuln/detail/CVE-2023-53730
Affected packages
Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Affected ranges
- Type
- GIT
- Repo
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
- Events
-
Introducedb0853ab4a238c54b8f97ca7dde1ae156e2bbd5e4Fixed8563b58a4360e648ce18f0e98a75a4be51667431Fixedeb120c0aff5ceab9c9c46b87f302465bbf2bbaedFixed8ceeb3fc86a83700bb1585c189006080a47e8506Fixed9279a1b74ad98039d5d44d26b9e7a9cfe655b6d3Fixed3376c4fe2db4aea2dc721a27a999c41fdb45b54fFixed8d211554679d0b23702bd32ba04aeac0c1c4f660