CVE-2023-53823 Details
Description
In the Linux kernel, the following vulnerability has been resolved: block/rq_qos: protect rq_qos apis with a new lock commit 50e34d78815e ("block: disable the elevator int del_gendisk") move rq_qos_exit() from disk_release() to del_gendisk(), this will introduce some problems: 1) If rq_qos_add() is triggered by enabling iocost/iolatency through cgroupfs, then it can concurrent with del_gendisk(), it's not safe to write 'q->rq_qos' concurrently. 2) Activate cgroup policy that is relied on rq_qos will call rq_qos_add() and blkcg_activate_policy(), and if rq_qos_exit() is called in the middle, null-ptr-dereference will be triggered in blkcg_activate_policy(). 3) blkg_conf_open_bdev() can call blkdev_get_no_open() first to find the disk, then if rq_qos_exit() from del_gendisk() is done before rq_qos_add(), then memory will be leaked. This patch add a new disk level mutex 'rq_qos_mutex': 1) The lock will protect rq_qos_exit() directly. 2) For wbt that doesn't relied on blk-cgroup, rq_qos_add() can only be called from disk initialization for now because wbt can't be destructed until rq_qos_exit(), so it's safe not to protect wbt for now. Hoever, in case that rq_qos dynamically destruction is supported in the furture, this patch also protect rq_qos_add() from wbt_init() directly, this is enough because blk-sysfs already synchronize writers with disk removal. 3) For iocost and iolatency, in order to synchronize disk removal and cgroup configuration, the lock is held after blkdev_get_no_open() from blkg_conf_open_bdev(), and is released in blkg_conf_exit(). In order to fix the above memory leak, disk_live() is checked after holding the new lock.
A vulnerability in the Linux kernel's block layer can lead to concurrent access issues with the request queue quality of service (rq_qos) APIs. This vulnerability arises from a change that moved the rq_qos_exit() function from disk_release() to del_gendisk(), creating a race condition. When rq_qos_add() is called by enabling iocost or iolatency through cgroupfs, it can overlap with del_gendisk(), leading to unsafe concurrent writes. Additionally, if rq_qos_exit() is invoked mid-process, it can cause a null pointer dereference in the blkcg_activate_policy() function. The vulnerability also allows for memory leaks if rq_qos_exit() is called before rq_qos_add() during disk management operations.
The vulnerability has been addressed by introducing a new mutex, 'rq_qos_mutex', at the disk level. This mutex protects the rq_qos_exit() function and synchronizes rq_qos_add() calls with disk removal processes. Users should ensure they are running a version of the Linux kernel that includes this patch.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Dec 9, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/16398b4638b5cd8c1dc95fc940a1591a801d53ce | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/a13bd91be22318768d55470cbc0b0f4488ef9edf | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/f54c4ab8ffecf621ab20fb6d2b194af93616cd7e | kernel.org |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 30, 2026 | CVE Modified | kernel.org |
| Aug 4, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Dec 9, 2025 | New CVE Received | kernel.org |
Volerion