BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2024
CVE-2024-39476High confidence

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

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Scheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
Distribution package intelligence

Ubuntu vendor package status

Canonical’s release and source-package findings are shown separately from local repository availability.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Ubuntu releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical record ↗Source updated 11 Sept 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
SSA-613116 · CSAF 2.0 · revision 3 · interimSiemens ProductCERTSSA-613116: Multiple Vulnerabilities in Third-Party Components in SINEC OS before V3.1
3 known not affected

The vendor explicitly states that these products are not affected by this CVE.

  • RUGGEDCOM RST2428P (6GK6242-6PA00)
  • SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family
  • SCALANCE XCM-/XRM-/XCH-/XRH-300 family
Summary
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
Remediation
No remediation text is recorded.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Select the national-authority views to include. The exact source language is shown on each matched advisory. Your choice is remembered on this device and encoded in the shareable URL.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2024-38001

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionScheduled

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.

Patch available
01

What, why and how

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.

What

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.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

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.

Why

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

How

An attacker operating through local access may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
local access → Improper Locking → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Local
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-667 ↗

CWE-667: Improper Locking. The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
CWE-667
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2024-1913Red Hat OpenShift Container Platform: Mehrere Schwachstellen

Ein entfernter anonymer oder lokaler Angreifer kann mehrere Schwachstellen in Red Hat OpenShift Container Platform ausnutzen, um seine Privilegien zu erhöhen, beliebigen Code auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen offenzulegen, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2025-0612IBM Security Guardium: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM Security Guardium ausnutzen, um Sicherheitsbeschränkungen zu umgehen, einen Denial-of-Service-Zustand herbeizuführen, beliebigen Code auszuführen und vertrauliche Informationen preiszugeben.

Official advisory ↗
BSI · German · WID-SEC-2024-1528Linux Kernel: Mehrere Schwachstellen

Ein lokaler Angreifer kann mehrere Schwachstellen im Linux-Kernel ausnutzen, um einen Denial-of-Service-Zustand zu erzeugen oder einen unspezifischen Angriff durchzuführen.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-38596 Référence CVE CVE-2024-38598 https://www.cve.org/CVERecord?id=CVE-2024-38598 Référence CVE CVE-2024-38608 https://www.cve.org/CVERecord?id=CVE-2024-38608 Référence CVE CVE-2024-38615 https://www.cve.org/CVERecord?id=CVE-2024-38615 Référence CVE CVE-2024-38619 https://www.cve.org/CVERecord?id=CVE-2024-38619 Référence CVE CVE-2024-38627 https://www.cve.org/CVERecord?id=CVE-2024-38627 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39472 https://www.cve.org/CVERecord?id=CVE-2024-39472 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=CVE-2024-39503 Référence CVE CVE-2024-39506 https://www.cve.org/CVERecord?id=CVE-2024-39506 Référence CVE CVE-2024-40679 https://www.cve.org/CVERecord?id=CVE-2024-40679 Référence CVE CVE-2024-40901 https://www.cve.org/CVERecord?id=CVE-2024-40901 Référence CVE CVE-2024-40904 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0677Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2024-36901 Référence CVE CVE-2024-36938 https://www.cve.org/CVERecord?id=CVE-2024-36938 Référence CVE CVE-2024-36974 https://www.cve.org/CVERecord?id=CVE-2024-36974 Référence CVE CVE-2024-36978 https://www.cve.org/CVERecord?id=CVE-2024-36978 Référence CVE CVE-2024-37078 https://www.cve.org/CVERecord?id=CVE-2024-37078 Référence CVE CVE-2024-38586 https://www.cve.org/CVERecord?id=CVE-2024-38586 Référence CVE CVE-2024-38619 https://www.cve.org/CVERecord?id=CVE-2024-38619 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39482 https://www.cve.org/CVERecord?id=CVE-2024-39482 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39499 https://www.cve.org/CVERecord?id=CVE-2024-39499 Référence CVE CVE-2024-39501 https://www.cve.org/CVERecord?id=CVE-2024-39501 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39503 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0024Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-26852 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-27051 https://www.cve.org/CVERecord?id=CVE-2024-27051 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36905 https://www.cve.org/CVERecord?id=CVE-2024-36905 Référence CVE CVE-2024-36954 https://www.cve.org/CVERecord?id=CVE-2024-36954 Référence CVE CVE-2024-38538 https://www.cve.org/CVERecord?id=CVE-2024-38538 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-40965 https://www.cve.org/CVERecord?id=CVE-2024-40965 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41082 https://www.cve.org/CVERecord?id=CVE-2024-41082 Référence CVE CVE-2024-42098 https://www.cve.org/CVERecord?id=CVE-2024-42098 Référence CVE CVE-2024-42114 https://www.cve.org/CVERecord?id=CVE-2024-42114 Référence CVE CVE-2024-42131 https://www.cve.org/CVERecord?id=CVE-2024-42131 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42229 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1102Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36953 Référence CVE CVE-2024-36954 https://www.cve.org/CVERecord?id=CVE-2024-36954 Référence CVE CVE-2024-36957 https://www.cve.org/CVERecord?id=CVE-2024-36957 Référence CVE CVE-2024-36968 https://www.cve.org/CVERecord?id=CVE-2024-36968 Référence CVE CVE-2024-38576 https://www.cve.org/CVERecord?id=CVE-2024-38576 Référence CVE CVE-2024-38577 https://www.cve.org/CVERecord?id=CVE-2024-38577 Référence CVE CVE-2024-38589 https://www.cve.org/CVERecord?id=CVE-2024-38589 Référence CVE CVE-2024-38599 https://www.cve.org/CVERecord?id=CVE-2024-38599 Référence CVE CVE-2024-38615 https://www.cve.org/CVERecord?id=CVE-2024-38615 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40965 https://www.cve.org/CVERecord?id=CVE-2024-40965 Référence CVE CVE-2024-40997 https://www.cve.org/CVERecord?id=CVE-2024-40997 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41023 https://www.cve.org/CVERecord?id=CVE-2024-41023 Référence CVE CVE-2024-41031 https://www.cve.org/CVERecord?id=CVE-2024-41031 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41049 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1048Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-35864 Référence CVE CVE-2024-35867 https://www.cve.org/CVERecord?id=CVE-2024-35867 Référence CVE CVE-2024-35905 https://www.cve.org/CVERecord?id=CVE-2024-35905 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35950 https://www.cve.org/CVERecord?id=CVE-2024-35950 Référence CVE CVE-2024-36899 https://www.cve.org/CVERecord?id=CVE-2024-36899 Référence CVE CVE-2024-36904 https://www.cve.org/CVERecord?id=CVE-2024-36904 Référence CVE CVE-2024-36964 https://www.cve.org/CVERecord?id=CVE-2024-36964 Référence CVE CVE-2024-38538 https://www.cve.org/CVERecord?id=CVE-2024-38538 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-40909 https://www.cve.org/CVERecord?id=CVE-2024-40909 Référence CVE CVE-2024-40954 https://www.cve.org/CVERecord?id=CVE-2024-40954 Référence CVE CVE-2024-40965 https://www.cve.org/CVERecord?id=CVE-2024-40965 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41059 https://www.cve.org/CVERecord?id=CVE-2024-41059 Référence CVE CVE-2024-41082 https://www.cve.org/CVERecord?id=CVE-2024-41082 Référence CVE CVE-2024-42114 https://www.cve.org/CVERecord?id=CVE-2024-42114 Référence CVE CVE-2024-42133 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0999Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-26943 Référence CVE CVE-2024-27026 https://www.cve.org/CVERecord?id=CVE-2024-27026 Référence CVE CVE-2024-27043 https://www.cve.org/CVERecord?id=CVE-2024-27043 Référence CVE CVE-2024-35980 https://www.cve.org/CVERecord?id=CVE-2024-35980 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36957 https://www.cve.org/CVERecord?id=CVE-2024-36957 Référence CVE CVE-2024-38576 https://www.cve.org/CVERecord?id=CVE-2024-38576 Référence CVE CVE-2024-38577 https://www.cve.org/CVERecord?id=CVE-2024-38577 Référence CVE CVE-2024-38599 https://www.cve.org/CVERecord?id=CVE-2024-38599 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-40965 https://www.cve.org/CVERecord?id=CVE-2024-40965 Référence CVE CVE-2024-41016 https://www.cve.org/CVERecord?id=CVE-2024-41016 Référence CVE CVE-2024-41031 https://www.cve.org/CVERecord?id=CVE-2024-41031 Référence CVE CVE-2024-41047 https://www.cve.org/CVERecord?id=CVE-2024-41047 Référence CVE CVE-2024-41082 https://www.cve.org/CVERecord?id=CVE-2024-41082 Référence CVE CVE-2024-42145 https://www.cve.org/CVERecord?id=CVE-2024-42145 Référence CVE CVE-2024-42226 https://www.cve.org/CVERecord?id=CVE-2024-42226 Référence CVE CVE-2024-42253 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0958Multiples vulnérabilités dans les produits IBM

d?id=CVE-2024-38615 Référence CVE CVE-2024-38627 https://www.cve.org/CVERecord?id=CVE-2024-38627 Référence CVE CVE-2024-38808 https://www.cve.org/CVERecord?id=CVE-2024-38808 Référence CVE CVE-2024-38809 https://www.cve.org/CVERecord?id=CVE-2024-38809 Référence CVE CVE-2024-38816 https://www.cve.org/CVERecord?id=CVE-2024-38816 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39331 https://www.cve.org/CVERecord?id=CVE-2024-39331 Référence CVE CVE-2024-39338 https://www.cve.org/CVERecord?id=CVE-2024-39338 Référence CVE CVE-2024-39472 https://www.cve.org/CVERecord?id=CVE-2024-39472 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39495 https://www.cve.org/CVERecord?id=CVE-2024-39495 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-39689 https://www.cve.org/CVERecord?id=CVE-2024-39689 Référence CVE CVE-2024-4032 https://www.cve.org/CVERecord?id=CVE-2024-4032 Référence CVE CVE-2024-4067 https://www.cve.org/CVERecord?id=CVE-2024-4067 Référence CVE CVE-2024-40902 https://www.cve.org/CVERecord?id=CVE-2024-40902 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0925Multiples vulnérabilités dans le noyau Linux de Red Hat

De multiples vulnérabilités ont été découvertes dans le noyau Linux de Red Hat. Certaines d'entre elles permettent à un attaquant de provoquer une élévation de privilèges, un contournement de la politique de sécurité et un déni de service.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0822Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36929 Référence CVE CVE-2024-36933 https://www.cve.org/CVERecord?id=CVE-2024-36933 Référence CVE CVE-2024-36939 https://www.cve.org/CVERecord?id=CVE-2024-36939 Référence CVE CVE-2024-36970 https://www.cve.org/CVERecord?id=CVE-2024-36970 Référence CVE CVE-2024-36979 https://www.cve.org/CVERecord?id=CVE-2024-36979 Référence CVE CVE-2024-38548 https://www.cve.org/CVERecord?id=CVE-2024-38548 Référence CVE CVE-2024-38563 https://www.cve.org/CVERecord?id=CVE-2024-38563 Référence CVE CVE-2024-38609 https://www.cve.org/CVERecord?id=CVE-2024-38609 Référence CVE CVE-2024-38662 https://www.cve.org/CVERecord?id=CVE-2024-38662 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39483 https://www.cve.org/CVERecord?id=CVE-2024-39483 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39486 https://www.cve.org/CVERecord?id=CVE-2024-39486 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39491 https://www.cve.org/CVERecord?id=CVE-2024-39491 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0779Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2024-36970 Référence CVE CVE-2024-36979 https://www.cve.org/CVERecord?id=CVE-2024-36979 Référence CVE CVE-2024-38548 https://www.cve.org/CVERecord?id=CVE-2024-38548 Référence CVE CVE-2024-38554 https://www.cve.org/CVERecord?id=CVE-2024-38554 Référence CVE CVE-2024-38563 https://www.cve.org/CVERecord?id=CVE-2024-38563 Référence CVE CVE-2024-38602 https://www.cve.org/CVERecord?id=CVE-2024-38602 Référence CVE CVE-2024-38609 https://www.cve.org/CVERecord?id=CVE-2024-38609 Référence CVE CVE-2024-38618 https://www.cve.org/CVERecord?id=CVE-2024-38618 Référence CVE CVE-2024-38662 https://www.cve.org/CVERecord?id=CVE-2024-38662 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39483 https://www.cve.org/CVERecord?id=CVE-2024-39483 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39486 https://www.cve.org/CVERecord?id=CVE-2024-39486 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39491 https://www.cve.org/CVERecord?id=CVE-2024-39491 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39497 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0728Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2024-35898 Référence CVE CVE-2024-35962 https://www.cve.org/CVERecord?id=CVE-2024-35962 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-38538 https://www.cve.org/CVERecord?id=CVE-2024-38538 Référence CVE CVE-2024-38540 https://www.cve.org/CVERecord?id=CVE-2024-38540 Référence CVE CVE-2024-38544 https://www.cve.org/CVERecord?id=CVE-2024-38544 Référence CVE CVE-2024-38579 https://www.cve.org/CVERecord?id=CVE-2024-38579 Référence CVE CVE-2024-38608 https://www.cve.org/CVERecord?id=CVE-2024-38608 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-40905 https://www.cve.org/CVERecord?id=CVE-2024-40905 Référence CVE CVE-2024-40911 https://www.cve.org/CVERecord?id=CVE-2024-40911 Référence CVE CVE-2024-40912 https://www.cve.org/CVERecord?id=CVE-2024-40912 Référence CVE CVE-2024-40914 https://www.cve.org/CVERecord?id=CVE-2024-40914 Référence CVE CVE-2024-40929 https://www.cve.org/CVERecord?id=CVE-2024-40929 Référence CVE CVE-2024-40939 https://www.cve.org/CVERecord?id=CVE-2024-40939 Référence CVE CVE-2024-40941 https://www.cve.org/CVERecord?id=CVE-2024-40941 Référence CVE CVE-2024-40957 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0668Multiples vulnérabilités dans le noyau Linux de Red Hat

d?id=CVE-2024-38573 Référence CVE CVE-2024-38575 https://www.cve.org/CVERecord?id=CVE-2024-38575 Référence CVE CVE-2024-38596 https://www.cve.org/CVERecord?id=CVE-2024-38596 Référence CVE CVE-2024-38598 https://www.cve.org/CVERecord?id=CVE-2024-38598 Référence CVE CVE-2024-38615 https://www.cve.org/CVERecord?id=CVE-2024-38615 Référence CVE CVE-2024-38627 https://www.cve.org/CVERecord?id=CVE-2024-38627 Référence CVE CVE-2024-38663 https://www.cve.org/CVERecord?id=CVE-2024-38663 Référence CVE CVE-2024-39276 https://www.cve.org/CVERecord?id=CVE-2024-39276 Référence CVE CVE-2024-39472 https://www.cve.org/CVERecord?id=CVE-2024-39472 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39502 https://www.cve.org/CVERecord?id=CVE-2024-39502 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40974 https://www.cve.org/CVERecord?id=CVE-2024-40974 Gestion détaillée du document le 09 août 2024 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0613Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2024-39298 Référence CVE CVE-2024-39301 https://www.cve.org/CVERecord?id=CVE-2024-39301 Référence CVE CVE-2024-39371 https://www.cve.org/CVERecord?id=CVE-2024-39371 Référence CVE CVE-2024-39467 https://www.cve.org/CVERecord?id=CVE-2024-39467 Référence CVE CVE-2024-39468 https://www.cve.org/CVERecord?id=CVE-2024-39468 Référence CVE CVE-2024-39469 https://www.cve.org/CVERecord?id=CVE-2024-39469 Référence CVE CVE-2024-39471 https://www.cve.org/CVERecord?id=CVE-2024-39471 Référence CVE CVE-2024-39474 https://www.cve.org/CVERecord?id=CVE-2024-39474 Référence CVE CVE-2024-39475 https://www.cve.org/CVERecord?id=CVE-2024-39475 Référence CVE CVE-2024-39476 https://www.cve.org/CVERecord?id=CVE-2024-39476 Référence CVE CVE-2024-39480 https://www.cve.org/CVERecord?id=CVE-2024-39480 Référence CVE CVE-2024-39482 https://www.cve.org/CVERecord?id=CVE-2024-39482 Référence CVE CVE-2024-39484 https://www.cve.org/CVERecord?id=CVE-2024-39484 Référence CVE CVE-2024-39487 https://www.cve.org/CVERecord?id=CVE-2024-39487 Référence CVE CVE-2024-39488 https://www.cve.org/CVERecord?id=CVE-2024-39488 Référence CVE CVE-2024-39489 https://www.cve.org/CVERecord?id=CVE-2024-39489 Référence CVE CVE-2024-39493 https://www.cve.org/CVERecord?id=CVE-2024-39493 Référence CVE CVE-2024-39494 https://www.cve.org/CVERecord?id=

Official advisory ↗
NCSC-NL · Dutch · NCSC-2024-0339Kwetsbaarheden verholpen in Microsoft Mariner

De kwetsbaarheden betreffen oudere kwetsbaarheden in diverse subcomponenten van de distro, zoals Python, Emacs, Qemu, Django, Curl, wget etc. welke in de nieuwe versie zijn verholpen.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Linux: f3d55bd5b7b928ad82f8075d89c908702f3593ab < b32aa95843cac6b12c2c014d40fca18aef24a347, 1c00bb624cd084e2006520ad0edacaff0fb941c4 < 634ba3c97ec413cb10681c7b196db43ee461ecf4, 782b3e71c957991ac8ae53318bc369049d49bb53 < aa64464c8f4d2ab92f6d0b959a1e0767b829d787, 9e86dffd0b02594d2e7c60c6db9e889c0395414b < 098d54934814dd876963abfe751c3b1cf7fbe56a, 5e2cf333b7bd5d3e62595a44d598a254c697cd74 < 3f8d5e802d4cedd445f9a89be8c3fd2d0e99024b, 5e2cf333b7bd5d3e62595a44d598a254c697cd74 < cd2538e5af495b3c747e503db346470fc1ffc447, 5e2cf333b7bd5d3e62595a44d598a254c697cd74 < e332a12f65d8fed8cf63bedb4e9317bb872b9ac7, 5e2cf333b7bd5d3e62595a44d598a254c697cd74 < 151f66bb618d1fd0eeb84acb61b4a9fa5d8bb0fa, 7d808fe6af8409cf9f46ed2b10840e5788985e9b, 2cab058f2b147e0b7c01546ba00445e5701861f5, 91962e40ec3d26e291db230cd45b302da2aff200, 4.19.262 < 4.19.316, 5.4.220 < 5.4.278, 5.10.150 < 5.10.219, 5.15.75 < 5.15.161, 4.14.296 < 4.15, 5.19.17 < 5.20, 6.0.3 < 6.1, 6.1
Fixed
Linux: < 6.1, 4.19.316 ≤ 4.19.*, 5.4.278 ≤ 5.4.*, 5.10.219 ≤ 5.10.*, 5.15.161 ≤ 5.15.*, 6.1.94 ≤ 6.1.*, 6.6.34 ≤ 6.6.*, 6.9.5 ≤ 6.9.*, 6.10 ≤ *
Action
Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 5 Jul 2024 · Last source change 23 May 2026, 15:50 UTC · CWE-667 · Improper Locking

CVE recordCVE.org · 5.2
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2024-38001
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2024-38001↗Vendor CSAF · Siemens ProductCERT↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2024-39476 · cve.blacktree.nl