CVE-2022-49406

Source
https://nvd.nist.gov/vuln/detail/CVE-2022-49406
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49406.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2022-49406
Related
Published
2025-02-26T07:01:17Z
Modified
2025-04-17T20:29:18Z
Downstream
Severity
  • 5.5 (Medium) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

In the Linux kernel, the following vulnerability has been resolved:

block: Fix potential deadlock in blkiarangesysfsshow()

When being read, a sysfs attribute is already protected against removal with the kobject node active reference counter. As a result, in blkiarangesysfsshow(), 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->sysfslock); [ 760.703565] lock(kn->active#385); [ 760.703573] lock(&q->sysfslock); [ 760.703579] lock(kn->active#385); [ 760.703587] [ 760.703587] * DEADLOCK *

Solve this by removing the mutexlock()/mutexunlock() calls from blkiarangesysfsshow().

References

Affected packages

Debian:12 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.18.5-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / linux

Package

Name
linux
Purl
pkg:deb/debian/linux?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
5.18.5-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}