NVD / CVE Program· CNA Linux

CVE-2024-26775: aoe: avoid potential deadlock at set_capacity

Noroxi assessment

Priority: Monitor (action score 22/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Linux Linux 19a77b27163820f793b4d022979ffdca8f659b77, 2499fa286fb010ceb289950050199f33c26667b9, 2d623c94fbba3554f4446ba6f3c764994e8b0d26.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 19a77b27163820f793b4d022979ffdca8f659b77, 2499fa286fb010ceb289950050199f33c26667b9, 2d623c94fbba3554f4446ba6f3c764994e8b0d26 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available

Denial of service

BDU:2025-04395

Published: Apr 3, 2024
Updated: Jun 17, 2026
EPSS: 0.1% · 7th percentile
CWE: CWE-667

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 22 / 40 · 5.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.1%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
linux	linux kernel	cpe:2.3:o:linux:linux_kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

linux linux kernelbefore 6.1.80
linux linux kernel6.2 and later · before 6.6.19
linux linux kernel6.7 and later · before 6.7.7
linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

Linux Linux
- 5.11affected
- a782483cc1f875355690625d8253a232f2581418 and later · before 2499fa286fb010ceb289950050199f33c26667b9affected · git
- a782483cc1f875355690625d8253a232f2581418 and later · before 2d623c94fbba3554f4446ba6f3c764994e8b0d26affected · git
- a782483cc1f875355690625d8253a232f2581418 and later · before 673629018ba04906899dcb631beec34d871f709caffected · git
- a782483cc1f875355690625d8253a232f2581418 and later · before 19a77b27163820f793b4d022979ffdca8f659b77affected · git
- a782483cc1f875355690625d8253a232f2581418 and later · before e169bd4fb2b36c4b2bee63c35c740c85daeb2e86affected · git
- before 5.11not affected · semver
- 5.15.189 and later · up to and including 5.15.*not affected · semver
- 6.1.80 and later · up to and including 6.1.*not affected · semver
- 6.6.19 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	linux	before 6.1.82-1	6.1.82-1
Debian:13	linux	before 6.7.7-1	6.7.7-1

Same product

linux: all records

Other highest-scoring records for the same primary product.

CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
90Now
CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
89Now
CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
85Now

Published before and after this one in the same product

← EarlierCVE-2024-26771Apr 3, 2024 · dmaengine: ti: edma: Add some null pointer checks to the edma_probe
22Monitor
← EarlierCVE-2024-26774Apr 3, 2024 · ext4: avoid dividing by 0 in mb_update_avg_fragment_size() when block bitmap corrupt
22Monitor
Later →CVE-2024-26776Apr 3, 2024 · spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Linux Linux	19a77b27163820f793b4d022979ffdca8f659b77	Vendor (CNA)
Linux Linux	2499fa286fb010ceb289950050199f33c26667b9	Vendor (CNA)
Linux Linux	2d623c94fbba3554f4446ba6f3c764994e8b0d26	Vendor (CNA)
Linux Linux	673629018ba04906899dcb631beec34d871f709c	Vendor (CNA)
Linux Linux	e169bd4fb2b36c4b2bee63c35c740c85daeb2e86	Vendor (CNA)
debian:linux	6.1.82-1 · Debian:12	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).