# CVE-2024-53689: linux: In the Linux kernel, the following vulnerability has been resolved:  block: Fix potential deadlock while freezing que...

CVE-2024-53689 is fixed in linux on 1 platform by CVE-2024-53689 (version 6.12.8-1), released January 11, 2025. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2024-53689
- Priority: Routine
- CVSS: 5.5 (medium)
- EPSS: n/a
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Jan 11, 2025

## Description

In the Linux kernel, the following vulnerability has been resolved:  block: Fix potential deadlock while freezing queue and acquiring sysfs_lock  For storing a value to a queue attribute, the queue_attr_store function first freezes the queue (->q_usage_counter(io)) and then acquire ->sysfs_lock. This seems not correct as the usual ordering should be to acquire ->sysfs_lock before freezing the queue. This incorrect ordering causes the following lockdep splat which we are able to reproduce always simply by accessing /sys/kernel/debug file using ls command:  [   57.597146] WARNING: possible circular locking dependency detected [   57.597154] 6.12.0-10553-gb86545e02e8c #20 Tainted: G        W [   57.597162] ------------------------------------------------------ [   57.597168] ls/4605 is trying to acquire lock: [   57.597176] c00000003eb56710 (&mm->mmap_lock){++++}-{4:4}, at: __might_fault+0x58/0xc0 [   57.597200]                but task is already holding lock: [   57.597207] c0000018e27c6810 (&sb->s_type->i_mutex_key#3){++++}-{4:4}, at: iterate_dir+0x94/0x1d4 [   57.597226]                which lock already depends on the new lock.  [   57.597233]                the existing dependency chain (in reverse order) is: [   57.597241]                -> #5 (&sb->s_type->i_mutex_key#3){++++}-{4:4}: [   57.597255]        down_write+0x6c/0x18c [   57.597264]        start_creating+0xb4/0x24c [   57.597274]        debugfs_create_dir+0x2c/0x1e8 [   57.597283]        blk_register_queue+0xec/0x294 [   57.597292]        add_disk_fwnode+0x2e4/0x548 [   57.597302]        brd_alloc+0x2c8/0x338 [   57.597309]        brd_init+0x100/0x178 [   57.597317]        do_one_initcall+0x88/0x3e4 [   57.597326]        kernel_init_freeable+0x3cc/0x6e0 [   57.597334]        kernel_init+0x34/0x1cc [   57.597342]        ret_from_kernel_user_thread+0x14/0x1c [   57.597350]                -> #4 (&q->debugfs_mutex){+.+.}-{4:4}: [   57.597362]        __mutex_lock+0xfc/0x12a0 [   57.597370]        blk_register_queue+0xd4/0x294 [   57.597379]        add_disk_fwnode+0x2e4/0x548 [   57.597388]        brd_alloc+0x2c8/0x338 [   57.597395]        brd_init+0x100/0x178 [   57.597402]        do_one_initcall+0x88/0x3e4 [   57.597410]        kernel_init_freeable+0x3cc/0x6e0 [   57.597418]        kernel_init+0x34/0x1cc [   57.597426]        ret_from_kernel_user_thread+0x14/0x1c [   57.597434]                -> #3 (&q->sysfs_lock){+.+.}-{4:4}: [   57.597446]        __mutex_lock+0xfc/0x12a0 [   57.597454]        queue_attr_store+0x9c/0x110 [   57.597462]        sysfs_kf_write+0x70/0xb0 [   57.597471]        kernfs_fop_write_iter+0x1b0/0x2ac [   57.597480]        vfs_write+0x3dc/0x6e8 [   57.597488]        ksys_write+0x84/0x140 [   57.597495]        system_call_exception+0x130/0x360 [   57.597504]        system_call_common+0x160/0x2c4 [   57.597516]                -> #2 (&q->q_usage_counter(io)#21){++++}-{0:0}: [   57.597530]        __submit_bio+0x5ec/0x828 [   57.597538]        submit_bio_noacct_nocheck+0x1e4/0x4f0 [   57.597547]        iomap_readahead+0x2a0/0x448 [   57.597556]        xfs_vm_readahead+0x28/0x3c [   57.597564]        read_pages+0x88/0x41c [   57.597571]        page_cache_ra_unbounded+0x1ac/0x2d8 [   57.597580]        filemap_get_pages+0x188/0x984 [   57.597588]        filemap_read+0x13c/0x4bc [   57.597596]        xfs_file_buffered_read+0x88/0x17c [   57.597605]        xfs_file_read_iter+0xac/0x158 [   57.597614]        vfs_read+0x2d4/0x3b4 [   57.597622]        ksys_read+0x84/0x144 [   57.597629]        system_call_exception+0x130/0x360 [   57.597637]        system_call_common+0x160/0x2c4 [   57.597647]                -> #1 (mapping.invalidate_lock#2){++++}-{4:4}: [   57.597661]        down_read+0x6c/0x220 [   57.597669]        filemap_fault+0x870/0x100c [   57.597677]        xfs_filemap_fault+0xc4/0x18c [   57.597684]        __do_fault+0x64/0x164 [   57.597693]        __handle_mm_fault+0x1274/0x1dac [   57.597702]        handle_mm_fault+0x248/0x48 ---truncated---

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | linux Debian 13.5 (trixie) | 6.12.8-1 | [CVE-2024-53689](https://patchblox.com/security/data/fix/linux/cve-2024-53689.md) | Jan 11, 2025 |

---

Data as of 2026-11-08T06:59:42Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.