CVE-2024-26775

aoe: avoid potential deadlock at set_capacity

MEDIUM
5.5
CVSS Score
Published: April 3, 2024 at 05:01 PM UTC
Updated: June 17, 2026 at 07:18 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: aoe: avoid potential deadlock at set_capacity Move set_capacity() outside of the section procected by (&d->lock). To avoid possible interrupt unsafe locking scenario: CPU0 CPU1 ---- ---- [1] lock(&bdev->bd_size_lock); local_irq_disable(); [2] lock(&d->lock); [3] lock(&bdev->bd_size_lock); <Interrupt> [4] lock(&d->lock); *** DEADLOCK *** Where [1](&bdev->bd_size_lock) hold by zram_add()->set_capacity(). [2]lock(&d->lock) hold by aoeblk_gdalloc(). And aoeblk_gdalloc() is trying to acquire [3](&bdev->bd_size_lock) at set_capacity() call. In this situation an attempt to acquire [4]lock(&d->lock) from aoecmd_cfg_rsp() will lead to deadlock. So the simplest solution is breaking lock dependency [2](&d->lock) -> [3](&bdev->bd_size_lock) by moving set_capacity() outside.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 6.1.805.11 ≤ v < 5.15.1895.11 ≤ v < 6.1.805.11 ≤ v < 6.6.195.11 ≤ v < 6.7.75.11 ≤ v < 6.86.2 ≤ v < 6.6.196.7 ≤ v < 6.7.76.8 rc1a782483cc1f875355690625d8253a232f2581418
Vendor states this is fixed in 19a77b27163820f793b4d022979ffdca8f659b77 (fixed)
Vendor states this is fixed in 2499fa286fb010ceb289950050199f33c26667b9 (fixed)
Vendor states this is fixed in 2d623c94fbba3554f4446ba6f3c764994e8b0d26 (fixed)
Vendor states this is fixed in 673629018ba04906899dcb631beec34d871f709c (fixed)
Vendor states this is fixed in e169bd4fb2b36c4b2bee63c35c740c85daeb2e86 (fixed)
Vendor states this is fixed in 5.11 (unaffected)
Vendor states this is fixed in 5.15.189 (unaffected)
Vendor states this is fixed in 6.1.80 (unaffected)
Vendor states this is fixed in 6.6.19 (unaffected)
Vendor states this is fixed in 6.7.7 (unaffected)
Vendor states this is fixed in 6.8 (unaffected)

References (5)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/19a77b27163820f793b4d022979ffdca8f659b77
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2d623c94fbba3554f4446ba6f3c764994e8b0d26
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/673629018ba04906899dcb631beec34d871f709c
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/e169bd4fb2b36c4b2bee63c35c740c85daeb2e86

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card