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

dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume

Linux · Linux

5.5MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityMediumOperational priority:Low, lowered one band.downgradedsince 23 May 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.20% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict local access and enforce least privilege on affected hosts.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: No default targetRemediation target: Normal maintenance

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

18 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 14 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

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.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.10.3-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.8Affected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, 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 Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, 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 Ubuntu Security ↗Source updated 5 Oct 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
CVE-2024-43820 · CSAF 2.0 · revision 63 · interimSUSE Product Security TeamCVE-2024-43820
31 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Desktop 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default-livepatch-devel as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Live Patching 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Server 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Server 15 SP6
  • kernel-source as component of SUSE Linux Enterprise Server 15 SP6
  • kernel-default as component of SUSE Linux Enterprise Server for SAP Applications 15 SP6
  • kernel-default-extra as component of SUSE Linux Enterprise Server for SAP Applications 15 SP6
Summary
In the Linux kernel, the following vulnerability has been resolved: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

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

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

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-40470

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 actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 14 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.

What

In the Linux kernel, the following vulnerability has been resolved: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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: dm-raid: Fix WARN_ON_ONCE check for sync_thread in raid_resume rm-raid devices will occasionally trigger the following warning when being resumed after a table load because DM_RECOVERY_RUNNING is set: WARNING: CPU: 7 PID: 5660 at drivers/md/dm-raid.c:4105 raid_resume+0xee/0x100 [dm_raid] The failing check is: WARN_ON_ONCE(test_bit(MD_RECOVERY_RUNNING, &mddev->recovery)); This check is designed to make sure that the sync thread isn't registered, but md_check_recovery can set MD_RECOVERY_RUNNING without the sync_thread ever getting registered. Instead of checking if MD_RECOVERY_RUNNING is set, check if sync_thread is non-NULL.

Why

The current structured CVE record identifies a security weakness, but the root cause requires confirmation in the linked vendor material.

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 → vulnerable operation → 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.
CWE not yet assigned
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.
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1439Dell Secure Connect Gateway: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein Angreifer kann mehrere Schwachstellen in Dell Secure Connect Gateway ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-1875Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240821Security Bulletin 21 Aug 2024

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 21 Aug 2024, published on 21 August 2024. Open the linked bulletin for the product, severity and reference information published in that issue.

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

ecord?id=CVE-2024-34750 Référence CVE CVE-2024-3651 https://www.cve.org/CVERecord?id=CVE-2024-3651 Référence CVE CVE-2024-36880 https://www.cve.org/CVERecord?id=CVE-2024-36880 Référence CVE CVE-2024-37891 https://www.cve.org/CVERecord?id=CVE-2024-37891 Référence CVE CVE-2024-38286 https://www.cve.org/CVERecord?id=CVE-2024-38286 Référence CVE CVE-2024-4032 https://www.cve.org/CVERecord?id=CVE-2024-4032 Référence CVE CVE-2024-42294 https://www.cve.org/CVERecord?id=CVE-2024-42294 Référence CVE CVE-2024-42316 https://www.cve.org/CVERecord?id=CVE-2024-42316 Référence CVE CVE-2024-42321 https://www.cve.org/CVERecord?id=CVE-2024-42321 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43821 https://www.cve.org/CVERecord?id=CVE-2024-43821 Référence CVE CVE-2024-43823 https://www.cve.org/CVERecord?id=CVE-2024-43823 Référence CVE CVE-2024-43898 https://www.cve.org/CVERecord?id=CVE-2024-43898 Référence CVE CVE-2024-46759 https://www.cve.org/CVERecord?id=CVE-2024-46759 Référence CVE CVE-2024-50067 https://www.cve.org/CVERecord?id=CVE-2024-50067 Référence CVE CVE-2024-50379 https://www.cve.org/CVERecord?id=CVE-2024-50379 Référence CVE CVE-2024-52316 https://www.cve.org/CVERecord?id=CVE-2024-52316 Référence CVE CVE-2024-52317 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-42268 Référence CVE CVE-2024-42278 https://www.cve.org/CVERecord?id=CVE-2024-42278 Référence CVE CVE-2024-42291 https://www.cve.org/CVERecord?id=CVE-2024-42291 Référence CVE CVE-2024-42294 https://www.cve.org/CVERecord?id=CVE-2024-42294 Référence CVE CVE-2024-42315 https://www.cve.org/CVERecord?id=CVE-2024-42315 Référence CVE CVE-2024-42316 https://www.cve.org/CVERecord?id=CVE-2024-42316 Référence CVE CVE-2024-42317 https://www.cve.org/CVERecord?id=CVE-2024-42317 Référence CVE CVE-2024-43816 https://www.cve.org/CVERecord?id=CVE-2024-43816 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=CVE-2024-43817 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43821 https://www.cve.org/CVERecord?id=CVE-2024-43821 Référence CVE CVE-2024-43826 https://www.cve.org/CVERecord?id=CVE-2024-43826 Référence CVE CVE-2024-43840 https://www.cve.org/CVERecord?id=CVE-2024-43840 Référence CVE CVE-2024-43842 https://www.cve.org/CVERecord?id=CVE-2024-43842 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-43870 https://www.cve.org/CVERecord?id=CVE-2024-43870 Référence CVE CVE-2024-43873 https://www.cve.org/CVERecord?id=CVE-2024-43873 Référence CVE CVE-2024-43874 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27415 Référence CVE CVE-2024-28956 https://www.cve.org/CVERecord?id=CVE-2024-28956 Référence CVE CVE-2024-35811 https://www.cve.org/CVERecord?id=CVE-2024-35811 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-35895 https://www.cve.org/CVERecord?id=CVE-2024-35895 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=CVE-2024-35910 Référence CVE CVE-2024-35914 https://www.cve.org/CVERecord?id=CVE-2024-35914 Référence CVE CVE-2024-38606 https://www.cve.org/CVERecord?id=CVE-2024-38606 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-45021 https://www.cve.org/CVERecord?id=CVE-2024-45021 Référence CVE CVE-2024-46713 https://www.cve.org/CVERecord?id=CVE-2024-46713 Référence CVE CVE-2024-46751 https://www.cve.org/CVERecord?id=CVE-2024-46751 Référence CVE CVE-2024-46752 https://www.cve.org/CVERecord?id=CVE-2024-46752 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46814 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-28956 Référence CVE CVE-2024-35826 https://www.cve.org/CVERecord?id=CVE-2024-35826 Référence CVE CVE-2024-35840 https://www.cve.org/CVERecord?id=CVE-2024-35840 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=CVE-2024-35910 Référence CVE CVE-2024-38606 https://www.cve.org/CVERecord?id=CVE-2024-38606 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41077 https://www.cve.org/CVERecord?id=CVE-2024-41077 Référence CVE CVE-2024-41149 https://www.cve.org/CVERecord?id=CVE-2024-41149 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43869 https://www.cve.org/CVERecord?id=CVE-2024-43869 Référence CVE CVE-2024-46713 https://www.cve.org/CVERecord?id=CVE-2024-46713 Référence CVE CVE-2024-46736 https://www.cve.org/CVERecord?id=CVE-2024-46736 Référence CVE CVE-2024-46763 https://www.cve.org/CVERecord?id=CVE-2024-46763 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46796 https://www.cve.org/CVERecord?id=CVE-2024-46796 Référence CVE CVE-2024-46865 https://www.cve.org/CVERecord?id=CVE-2024-46865 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-38606 Référence CVE CVE-2024-41005 https://www.cve.org/CVERecord?id=CVE-2024-41005 Référence CVE CVE-2024-41077 https://www.cve.org/CVERecord?id=CVE-2024-41077 Référence CVE CVE-2024-41092 https://www.cve.org/CVERecord?id=CVE-2024-41092 Référence CVE CVE-2024-41149 https://www.cve.org/CVERecord?id=CVE-2024-41149 Référence CVE CVE-2024-42098 https://www.cve.org/CVERecord?id=CVE-2024-42098 Référence CVE CVE-2024-42229 https://www.cve.org/CVERecord?id=CVE-2024-42229 Référence CVE CVE-2024-42240 https://www.cve.org/CVERecord?id=CVE-2024-42240 Référence CVE CVE-2024-42307 https://www.cve.org/CVERecord?id=CVE-2024-42307 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-46736 https://www.cve.org/CVERecord?id=CVE-2024-46736 Référence CVE CVE-2024-46782 https://www.cve.org/CVERecord?id=CVE-2024-46782 Référence CVE CVE-2024-46796 https://www.cve.org/CVERecord?id=CVE-2024-46796 Référence CVE CVE-2024-47408 https://www.cve.org/CVERecord?id=CVE-2024-47408 Référence CVE CVE-2024-47678 https://www.cve.org/CVERecord?id=CVE-2024-47678 Référence CVE CVE-2024-47794 https://www.cve.org/CVERecord?id=CVE-2024-47794 Référence CVE CVE-2024-49571 https://www.cve.org/CVERecord?id=CVE-2024-49571 Référence CVE CVE-2024-49924 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0022Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42317 Référence CVE CVE-2024-42318 https://www.cve.org/CVERecord?id=CVE-2024-42318 Référence CVE CVE-2024-42319 https://www.cve.org/CVERecord?id=CVE-2024-42319 Référence CVE CVE-2024-42320 https://www.cve.org/CVERecord?id=CVE-2024-42320 Référence CVE CVE-2024-42321 https://www.cve.org/CVERecord?id=CVE-2024-42321 Référence CVE CVE-2024-42322 https://www.cve.org/CVERecord?id=CVE-2024-42322 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=CVE-2024-43817 Référence CVE CVE-2024-43818 https://www.cve.org/CVERecord?id=CVE-2024-43818 Référence CVE CVE-2024-43819 https://www.cve.org/CVERecord?id=CVE-2024-43819 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43821 https://www.cve.org/CVERecord?id=CVE-2024-43821 Référence CVE CVE-2024-43823 https://www.cve.org/CVERecord?id=CVE-2024-43823 Référence CVE CVE-2024-43824 https://www.cve.org/CVERecord?id=CVE-2024-43824 Référence CVE CVE-2024-43825 https://www.cve.org/CVERecord?id=CVE-2024-43825 Référence CVE CVE-2024-43826 https://www.cve.org/CVERecord?id=CVE-2024-43826 Référence CVE CVE-2024-43827 https://www.cve.org/CVERecord?id=CVE-2024-43827 Référence CVE CVE-2024-43828 https://www.cve.org/CVERecord?id=CVE-2024-43828 Référence CVE CVE-2024-43829 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-1080Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2024-42317 Référence CVE CVE-2024-42318 https://www.cve.org/CVERecord?id=CVE-2024-42318 Référence CVE CVE-2024-42319 https://www.cve.org/CVERecord?id=CVE-2024-42319 Référence CVE CVE-2024-42320 https://www.cve.org/CVERecord?id=CVE-2024-42320 Référence CVE CVE-2024-42321 https://www.cve.org/CVERecord?id=CVE-2024-42321 Référence CVE CVE-2024-42322 https://www.cve.org/CVERecord?id=CVE-2024-42322 Référence CVE CVE-2024-43817 https://www.cve.org/CVERecord?id=CVE-2024-43817 Référence CVE CVE-2024-43818 https://www.cve.org/CVERecord?id=CVE-2024-43818 Référence CVE CVE-2024-43819 https://www.cve.org/CVERecord?id=CVE-2024-43819 Référence CVE CVE-2024-43820 https://www.cve.org/CVERecord?id=CVE-2024-43820 Référence CVE CVE-2024-43821 https://www.cve.org/CVERecord?id=CVE-2024-43821 Référence CVE CVE-2024-43823 https://www.cve.org/CVERecord?id=CVE-2024-43823 Référence CVE CVE-2024-43824 https://www.cve.org/CVERecord?id=CVE-2024-43824 Référence CVE CVE-2024-43825 https://www.cve.org/CVERecord?id=CVE-2024-43825 Référence CVE CVE-2024-43826 https://www.cve.org/CVERecord?id=CVE-2024-43826 Référence CVE CVE-2024-43827 https://www.cve.org/CVERecord?id=CVE-2024-43827 Référence CVE CVE-2024-43828 https://www.cve.org/CVERecord?id=CVE-2024-43828 Référence CVE CVE-2024-43829 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028981Linux の Linux Kernel における脆弱性

Linux の Linux Kernel には、不特定の脆弱性が存在します。

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.
Fix availability varies by product
Affected
Fixed
Linux: < 6.9, 6.10.3 ≤ 6.10.*, 6.11 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04

Evidence and provenance

Published 17 Aug 2024 · Last source change 23 May 2026, 15:52 UTC · CWE not yet assigned

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-40470
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceUnavailable
NVD statusNVD enriched

Missing structured fields: CWE classification. Missing data is not evidence of low risk; review the primary advisory.

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-40470↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor 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-43820 · cve.blacktree.nl