{"id":"DEBIAN-CVE-2023-53823","details":"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-\u003erq_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.","modified":"2026-11-15T18:00:13.732794925Z","published":"2025-12-09T16:17:21.107Z","upstream":["CVE-2023-53823"],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2023-53823"}],"affected":[{"package":{"name":"linux","ecosystem":"Debian:12","purl":"pkg:deb/debian/linux?arch=source&distro=bookworm"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.1.192-1"}]}],"versions":["6.1.106-1","6.1.106-2","6.1.106-3","6.1.112-1","6.1.115-1","6.1.119-1","6.1.123-1","6.1.124-1","6.1.128-1","6.1.129-1","6.1.133-1","6.1.135-1","6.1.137-1","6.1.139-1","6.1.140-1","6.1.147-1","6.1.148-1","6.1.153-1","6.1.158-1","6.1.159-1","6.1.162-1","6.1.164-1","6.1.170-1","6.1.170-2","6.1.170-3","6.1.172-1","6.1.174-1","6.1.176-1","6.1.177-1","6.1.180-1","6.1.187-1","6.1.190-1","6.1.27-1","6.1.37-1","6.1.38-1","6.1.38-2","6.1.38-2~bpo11+1","6.1.38-3","6.1.38-4","6.1.38-4~bpo11+1","6.1.52-1","6.1.55-1","6.1.55-1~bpo11+1","6.1.64-1","6.1.66-1","6.1.67-1","6.1.69-1","6.1.69-1~bpo11+1","6.1.76-1","6.1.76-1~bpo11+1","6.1.82-1","6.1.85-1","6.1.90-1","6.1.90-1~bpo11+1","6.1.94-1","6.1.94-1~bpo11+1","6.1.98-1","6.1.99-1"],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53823.json"}},{"package":{"name":"linux","ecosystem":"Debian:13","purl":"pkg:deb/debian/linux?arch=source&distro=trixie"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.4-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53823.json"}},{"package":{"name":"linux","ecosystem":"Debian:14","purl":"pkg:deb/debian/linux?arch=source&distro=forky"},"ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"6.4.4-1"}]}],"ecosystem_specific":{"urgency":"not yet assigned"},"database_specific":{"source":"https://storage.googleapis.com/osv-test-debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53823.json"}}],"schema_version":"1.9.2","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"}]}