Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

[REJECTED CVE] A vulnerability was identified in the Linux kernel’s block subsystem, where the queue_attr_store function incorrectly acquires the sysfs_lock after freezing the queue, leading to a potential deadlock. This incorrect locking order triggers a circular locking dependency, which can be consistently reproduced by simply accessing /sys/kernel/debug via the ls command. An attacker could exploit this issue by inducing race conditions through repeated file system access, potentially causing a denial-of-service (DoS) by forcing the system into an unrecoverable deadlock.

Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.

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] c0000018e2...