Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-39476: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING

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.17% (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 098d54934814dd876963abfe751c3b1cf7fbe56a, 151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa, 3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 -.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 098d54934814dd876963abfe751c3b1cf7fbe56a, 151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa, 3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b; azl3 kernel 6.6.22.1-2 on Azure Linux 3.0 6.6.35.1-5; azl3 kernel 6.6.35.1-5 on Azure Linux 3.0 - 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: md/raid5: fix deadlock that raid5d() wait for itself to clear MD_SB_CHANGE_PENDING Xiao reported that lvm2 test lvconvert-raid-takeover.sh can hang with small possibility, the root cause is exactly the same as commit bed9e27baf52 ("Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d"") However, Dan reported another hang after that, and junxiao investigated the problem and found out that this is caused by plugged bio can't issue from raid5d(). Current implementation in raid5d() has a weird dependence: 1) md_check_recovery() from raid5d() must hold 'reconfig_mutex' to clear MD_SB_CHANGE_PENDING; 2) raid5d() handles IO in a deadloop, until all IO are issued; 3) IO from raid5d() must wait for MD_SB_CHANGE_PENDING to be cleared; This behaviour is introduce before v2.6, and for consequence, if other context hold 'reconfig_mutex', and md_check_recovery() can't update super_block, then raid5d() will waste one cpu 100% by the deadloop, until 'reconfig_mutex' is released. Refer to the implementation from raid1 and raid10, fix this problem by skipping issue IO if MD_SB_CHANGE_PENDING is still set after md_check_recovery(), daemon thread will be woken up when 'reconfig_mutex' is released. Meanwhile, the hang problem will be fixed as well.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Jul 5, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 7th percentile

Report tools

JSON

Action score

22

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.

Follow CVE-2024-39476

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

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.

VendorProduct
linuxlinux kernel

Affected versions

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

  • linux linux kernel4.19 and later · before 4.19.316
  • linux linux kernel5.4 and later · before 5.4.278
  • linux linux kernel5.10 and later · before 5.10.219
  • linux linux kernel5.15 and later · before 5.15.161
  • linux linux kernel6.1 and later · before 6.1.94
  • linux linux kernel6.6 and later · before 6.6.34
  • linux linux kernel6.9 and later · before 6.9.5

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

    • 7d808fe6af8409cf9f46ed2b10840e5788985e9b, 2cab058f2b147e0b7c01546ba00445e5701861f5, 91962e40ec3d26e291db230cd45b302da2aff200, 6.1affected
    • f3d55bd5b7b928ad82f8075d89c908702f3593ab and later · before b32aa95843cac6b12c2c014d40fca18aef24a347affected · git
    • 1c00bb624cd084e2006520ad0edacaff0fb941c4 and later · before 634ba3c97ec413cb10681c7b196db43ee461ecf4affected · git
    • 782b3e71c957991ac8ae53318bc369049d49bb53 and later · before aa64464c8f4d2ab92f6d0b959a1e0767b829d787affected · git
    • 9e86dffd0b02594d2e7c60c6db9e889c0395414b and later · before 098d54934814dd876963abfe751c3b1cf7fbe56aaffected · git
    • 5e2cf333b7bd5d3e62595a44d598a254c697cd74 and later · before 3f8d5e802d4cedd445f9a89be8c3fd2d0e99024baffected · git
    • 5e2cf333b7bd5d3e62595a44d598a254c697cd74 and later · before cd2538e5af495b3c747e503db346470fc1ffc447affected · git
    • 5e2cf333b7bd5d3e62595a44d598a254c697cd74 and later · before e332a12f65d8fed8cf63bedb4e9317bb872b9ac7affected · git
    • 5e2cf333b7bd5d3e62595a44d598a254c697cd74 and later · before 151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0faaffected · git
    • 4.19.262 and later · before 4.19.316affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.94-16.1.94-1
Debian:13linuxbefore 6.9.7-16.9.7-1
Red Hat:rhel_eus:8.8::baseosbpftoolbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseosbpftool-debuginfobefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernelbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-abi-stablelistsbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-corebefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debugbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-corebefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-debuginfobefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-develbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modulesbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debug-modules-extrabefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfobefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-aarch64before 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-ppc64lebefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-s390xbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-debuginfo-common-x86_64before 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-develbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-docbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modulesbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-modules-extrabefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-toolsbefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8
Red Hat:rhel_eus:8.8::baseoskernel-tools-debuginfobefore 0:4.18.0-477.75.1.el8_80:4.18.0-477.75.1.el8_8

+12

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-39474Jul 5, 2024 · mm/vmalloc: fix vmalloc which may return null if called with __GFP_NOFAIL
    22Monitor
  • ← EarlierCVE-2024-39475Jul 5, 2024 · fbdev: savage: Handle err return when savagefb_check_var failed
    22Monitor
  • Later →CVE-2024-39477Jul 5, 2024 · mm/hugetlb: do not call vma_add_reservation upon ENOMEM
    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 / packageFixed versionSource
Linux Linux098d54934814dd876963abfe751c3b1cf7fbe56aVendor (CNA)
Linux Linux151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0faVendor (CNA)
Linux Linux3f8d5e802d4cedd445f9a89be8c3fd2d0e99024bVendor (CNA)
Linux Linux4.15Vendor (CNA)
Linux Linux4.19.316Vendor (CNA)
Linux Linux5.10.219Vendor (CNA)
Linux Linux5.15.161Vendor (CNA)
Linux Linux5.20Vendor (CNA)
Linux Linux5.4.278Vendor (CNA)
Linux Linux6.1Vendor (CNA)
Linux Linux634ba3c97ec413cb10681c7b196db43ee461ecf4Vendor (CNA)
Linux Linuxaa64464c8f4d2ab92f6d0b959a1e0767b829d787Vendor (CNA)
Linux Linuxb32aa95843cac6b12c2c014d40fca18aef24a347Vendor (CNA)
Linux Linuxcd2538e5af495b3c747e503db346470fc1ffc447Vendor (CNA)
Linux Linuxe332a12f65d8fed8cf63bedb4e9317bb872b9ac7Vendor (CNA)
azl3 kernel 6.6.22.1-2 on Azure Linux 3.06.6.35.1-5 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 kernel 6.6.35.1-5 on Azure Linux 3.0- · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.160.1-1 on CBL Mariner 2.05.15.162.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
cbl2 kernel 5.15.162.2-1 on CBL Mariner 2.05.15.162.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)
red hat:kernel-debug-modules0:4.18.0-477.75.1.el8_8 · Red Hat:rhel_eus:8.8::baseosPackage registry (OSV)

+2

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).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • 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.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (7 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records