First published: Wed Feb 26 2025(Updated: )
In the Linux kernel, the following vulnerability has been resolved: block: Fix potential deadlock in blk_ia_range_sysfs_show() When being read, a sysfs attribute is already protected against removal with the kobject node active reference counter. As a result, in blk_ia_range_sysfs_show(), there is no need to take the queue sysfs lock when reading the value of a range attribute. Using the queue sysfs lock in this function creates a potential deadlock situation with the disk removal, something that a lockdep signals with a splat when the device is removed: [ 760.703551] Possible unsafe locking scenario: [ 760.703551] [ 760.703554] CPU0 CPU1 [ 760.703556] ---- ---- [ 760.703558] lock(&q->sysfs_lock); [ 760.703565] lock(kn->active#385); [ 760.703573] lock(&q->sysfs_lock); [ 760.703579] lock(kn->active#385); [ 760.703587] [ 760.703587] *** DEADLOCK *** Solve this by removing the mutex_lock()/mutex_unlock() calls from blk_ia_range_sysfs_show().
Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Software | Affected Version | How to fix |
---|---|---|
Linux Kernel | ||
Linux Kernel | >=5.16<5.17.14 | |
Linux Kernel | >=5.18<5.18.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-49406 has been classified as a moderate severity vulnerability in the Linux kernel.
To fix CVE-2022-49406, update your Linux kernel to a version that is patched, specifically versions 5.18.4 or later.
CVE-2022-49406 affects multiple versions of the Linux kernel, specifically versions between 5.16 and 5.18.3.
CVE-2022-49406 is a block subsystem vulnerability related to potential deadlock scenarios in sysfs read operations.
While CVE-2022-49406 may lead to deadlock conditions, it does not directly allow for code execution or privilege escalation, making it less likely to be exploited.