CVE-2024-27023

md: Fix missing release of 'active_io' for flush

MEDIUM
5.5
CVSS Score
Published: May 1, 2024 at 12:49 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.3%
SSVC
No known exploit

Description

In the Linux kernel, the following vulnerability has been resolved: md: Fix missing release of 'active_io' for flush submit_flushes atomic_set(&mddev->flush_pending, 1); rdev_for_each_rcu(rdev, mddev) atomic_inc(&mddev->flush_pending); bi->bi_end_io = md_end_flush submit_bio(bi); /* flush io is done first */ md_end_flush if (atomic_dec_and_test(&mddev->flush_pending)) percpu_ref_put(&mddev->active_io) -> active_io is not released if (atomic_dec_and_test(&mddev->flush_pending)) -> missing release of active_io For consequence, mddev_suspend() will wait for 'active_io' to be zero forever. Fix this problem by releasing 'active_io' in submit_flushes() if 'flush_pending' is decreased to zero.

Affected

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

6.1.75 ≤ v < 6.1.806.6.14 ≤ v < 6.6.196.7.2 ≤ v < 6.7.7530cec617f5a8ba6f26bcbf0d64d75c951d177306.1.756.6.146.7.26.8 rc16.8 rc26.8 rc36.8 rc46.8 rc5c4c2345214b66e2505a26fd2ea58839dd7a1d48df9f2d957a8ea93c73182aebf7de30935a58c027dfa2bbff7b0b4e211fec5e5686ef96350690597b5
Vendor states this is fixed in 02dad157ba11064d073f5499dc33552b227d5d3a (fixed)
Vendor states this is fixed in 11f81438927f84edfaaeb5d5f10856c3a1c1fc82 (fixed)
Vendor states this is fixed in 6b2ff10390b19a2364af622b6666b690443f9f3f (fixed)
Vendor states this is fixed in 855678ed8534518e2b428bcbcec695de9ba248e8 (fixed)
Affected range stops below 6.1.80, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.19, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.7.7, so it looks safe — our inference, not a vendor statement

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/02dad157ba11064d073f5499dc33552b227d5d3a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/11f81438927f84edfaaeb5d5f10856c3a1c1fc82
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6b2ff10390b19a2364af622b6666b690443f9f3f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/855678ed8534518e2b428bcbcec695de9ba248e8

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

StatusANALYZED
CWE
NVD-CWE-noinfo

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