CVE-2024-26775: aoe: avoid potential deadlock at set_capacity
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.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue is a potential deadlock in the ATA over Ethernet code path. In business terms, it could affect system availability if a vulnerable kernel reaches the affected storage handling path. The source bundle does not provide a CVSS score, confirmed exploitation, or broad product impact beyond Linux.
Executive priority
Treat as a targeted availability risk for Linux systems using aoe, not as an emergency internet-wide issue based on current evidence. Patch through normal kernel maintenance, prioritizing affected storage-dependent systems.
Technical view
The CVE describes a lock-order problem in the Linux kernel aoe driver. set_capacity() was called while d->lock was held, creating a possible deadlock with bd_size_lock and interrupt-side aoe handling. The fix moves set_capacity() outside the protected section to break the dependency.
Likely exposure
Exposure is most likely on Linux systems running affected kernels where the aoe kernel driver is present, loaded, or operationally relevant. The provided data does not prove exposure for systems that do not use ATA over Ethernet.
Exploitation context
The source bundle marks KEV as false and provides no cited evidence of active exploitation. The issue is described as a potential kernel deadlock, indicating availability risk rather than confirmed code execution or privilege escalation.
Researcher notes
Evidence is limited to the CVE record and kernel stable references. No CVSS, CWE, exploit status, or distribution package matrix is included. The technical root cause is a lock dependency between d->lock and bd_size_lock around set_capacity().
Mitigation direction
Install Linux kernel or distribution updates containing the stable aoe deadlock fix.
Prioritize systems using or loading the aoe kernel driver.
Track the referenced stable kernel commits in custom kernel builds.
Check distribution advisories for corrected package versions.
If aoe is unused, follow vendor guidance on disabling or avoiding it.
Validation and detection
Inventory running kernel versions across Linux assets.
Check whether the aoe module is installed, loaded, or required.
Compare deployed kernels against vendor advisories and referenced stable commits.
Confirm patched kernels are booted, not only installed.
Review monitoring for unexplained kernel hangs or storage-path lockups.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2024-26775 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.