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

maple_tree: correct tree corruption on spanning store

Linux · Linux

7.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 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 severityHighOperational priority:Medium, lowered one band.downgradedsince 5 Aug 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • Exploitation requires an existing local or physical foothold with privileges.
  • EPSS is 0.21% 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: As exposure requiresRemediation target: Within 365 days

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

23 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 19 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.11.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.115-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.5-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.11.5-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-azure-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-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-nvidia-tegraAffected, 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.11Affected, 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-raspi-realtimeAffected, 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-realtimeAffected, 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
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, 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-50200 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: maple_tree: correct tree corruption on spanning store
22 known affected

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

  • kernel-rt as a component of Red Hat Enterprise Linux 9
  • kernel-rt-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-devel-matched as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-core as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-extra as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-internal as a component of Red Hat Enterprise Linux 9
  • kernel-rt-debug-modules-partner as a component of Red Hat Enterprise Linux 9
Summary
A flaw was found in the Linux kernel's maple tree implementation. A local attacker could exploit a tree corruption bug when performing a spanning store operation across two leaf nodes under specific conditions. This can lead to the mistaken duplication of entries, resulting in maple tree corruption. This corruption may allow an attacker to cause a denial of service or potentially gain unauthorized access to sensitive information.
Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect.
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-44702

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 19 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: maple_tree: correct tree corruption on spanning store Patch series "maple_tree: correct tree corruption on spanning store", v3. There has been a nasty yet subtle maple tree corruption bug that appears to have been in existence since the inception of the algorithm. This bug seems far more likely to happen since commit f8d112a4e657 ("mm/mmap: avoid zeroing vma tree in mmap_region()"), which is the point at which reports started to be submitted concerning this bug. We were made definitely aware of the bug thanks to the kind efforts of Bert Karwatzki who helped enormously in my being able to track this down and identify the cause of it. The bug arises when an attempt is made to perform a spanning store across two leaf nodes, where the right leaf node is the rightmost child of the shared parent, AND the store completely consumes the right-mode node. This results in mas_wr_spanning_store() mitakenly duplicating the new and existing entries at the maximum pivot within the range, and thus maple tree corruption. The fix patch corrects this by detecting this scenario and disallowing the mistaken duplicate copy. The fix patch commit message goes into great detail as to how this occurs. This series also includes a test which reliably reproduces the issue, and asserts that the fix works correctly. Bert has kindly tested the fix and confirmed it resolved his issues. Also Mikhail Gavrilov kindly reported what appears to be precisely the same bug, which this fix should also resolve. This patch (of 2): There has been a subtle bug present in the maple tree implementation from its inception. This arises from how stores are performed - when a store occurs, it will overwrite overlapping ranges and adjust the tree as necessary to accommodate this. A range may always ultimately span two leaf nodes. In this instance we walk the two leaf nodes, determine which elements are not overwritten to the left and to the right of the start and end of the ranges respectively and then rebalance the tree to contain these entries and the newly inserted one. This kind of store is dubbed a 'spanning store' and is implemented by mas_wr_spanning_store(). In order to reach this stage, mas_store_gfp() invokes mas_wr_preallocate(), mas_wr_store_type() and mas_wr_walk() in turn to walk the tree and update the object (mas) to traverse to the location where the write should be performed, determining its store type. When a spanning store is required, this function returns false stopping at the parent node which contains the target range, and mas_wr_store_type() marks the mas->store_type as wr_spanning_store to denote this fact. When we go to perform the store in mas_wr_spanning_store(), we first determine the elements AFTER the END of the range we wish to store (that is, to the right of the entry to be inserted) - we do this by walking to the NEXT pivot in the tree (i.e. r_mas.last + 1), starting at the node we have just determined contains the range over which we intend to write. We then turn our attention to the entries to the left of the entry we are inserting, whose state is represented by l_mas, and copy these into a 'big node', which is a special node which contains enough slots to contain two leaf node's worth of data. We then copy the entry we wish to store immediately after this - the copy and the insertion of the new entry is performed by mas_store_b_node(). After this we copy the elements to the right of the end of the range which we are inserting, if we have not exceeded the length of the node (i.e. r_mas.offset <= r_mas.end). Herein lies the bug - under very specific circumstances, this logic can break and corrupt the maple tree. Consider the following tree: Height 0 Root Node / \ pivot = 0xffff / \ pivot = ULONG_MAX / ---truncated---

What

In the Linux kernel, the following vulnerability has been resolved: maple_tree: correct tree corruption on spanning store Patch series "maple_tree: correct tree corruption on spanning store", v3. There has been a nasty yet subtle maple tree corruption bug that appears to have been in existence since the inception of the algorithm. This bug seems far more likely to happen since commit f8d112a4e657 ("mm/mmap: avoid zeroing vma tree in mmap_region()"), which is the point at which reports started to be submitted concerning this bug. We were made definitely aware of the bug thanks to the kind efforts of Bert Karwatzki who helped enormously in my being able to track this down and identify the cause of it. The bug arises when an attempt is made to perform a spanning store across two leaf nodes, where the right leaf node is the rightmost child of the shared parent, AND the store completely consumes the right-mode node. This results in mas_wr_spanning_store() mitakenly duplicating the new and existing entries at the maximum pivot within the range, and thus maple tree corruption. The fix patch corrects this by detecting this scenario and disallowing the mistaken duplicate copy. The fix patch commit message goes into great detail as to how this occurs. This series also includes a test which reliably reproduces the issue, and asserts that the fix works correctly. Bert has kindly tested the fix and confirmed it resolved his issues. Also Mikhail Gavrilov kindly reported what appears to be precisely the same bug, which this fix should also resolve. This patch (of 2): There has been a subtle bug present in the maple tree implementation from its inception. This arises from how stores are performed - when a store occurs, it will overwrite overlapping ranges and adjust the tree as necessary to accommodate this. A range may always ultimately span two leaf nodes. In this instance we walk the two leaf nodes, determine which elements are not overwritten to the left and to the right of the start and end of the ranges respectively and then rebalance the tree to contain these entries and the newly inserted one. This kind of store is dubbed a 'spanning store' and is implemented by mas_wr_spanning_store(). In order to reach this stage, mas_store_gfp() invokes mas_wr_preallocate(), mas_wr_store_type() and mas_wr_walk() in turn to walk the tree and update the object (mas) to traverse to the location where the write should be performed, determining its store type. When a spanning store is required, this function returns false stopping at the parent node which contains the target range, and mas_wr_store_type() marks the mas->store_type as wr_spanning_store to denote this fact. When we go to perform the store in mas_wr_spanning_store(), we first determine the elements AFTER the END of the range we wish to store (that is, to the right of the entry to be inserted) - we do this by walking to the NEXT pivot in the tree (i.e. r_mas.last + 1), starting at the node we have just determined contains the range over which we intend to write. We then turn our attention to the entries to the left of the entry we are inserting, whose state is represented by l_mas, and copy these into a 'big node', which is a special node which contains enough slots to contain two leaf node's worth of data. We then copy the entry we wish to store immediately after this - the copy and the insertion of the new entry is performed by mas_store_b_node(). After this we copy the elements to the right of the end of the range which we are inserting, if we have not exceeded the length of the node (i.e. r_mas.offset <= r_mas.end). Herein lies the bug - under very specific circumstances, this logic can break and corrupt the maple tree. Consider the following tree: Height 0 Root Node / \ pivot = 0xffff / \ pivot = ULONG_MAX / ---truncated---

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: maple_tree: correct tree corruption on spanning store Patch series "maple_tree: correct tree corruption on spanning store", v3. There has been a nasty yet subtle maple tree corruption bug that appears to have been in existence since the inception of the algorithm. This bug seems far more likely to happen since commit f8d112a4e657 ("mm/mmap: avoid zeroing vma tree in mmap_region()"), which is the point at which reports started to be submitted concerning this bug. We were made definitely aware of the bug thanks to the kind efforts of Bert Karwatzki who helped enormously in my being able to track this down and identify the cause of it. The bug arises when an attempt is made to perform a spanning store across two leaf nodes, where the right leaf node is the rightmost child of the shared parent, AND the store completely consumes the right-mode node. This results in mas_wr_spanning_store() mitakenly duplicating the new and existing entries at the maximum pivot within the range, and thus maple tree corruption. The fix patch corrects this by detecting this scenario and disallowing the mistaken duplicate copy. The fix patch commit message goes into great detail as to how this occurs. This series also includes a test which reliably reproduces the issue, and asserts that the fix works correctly. Bert has kindly tested the fix and confirmed it resolved his issues. Also Mikhail Gavrilov kindly reported what appears to be precisely the same bug, which this fix should also resolve. This patch (of 2): There has been a subtle bug present in the maple tree implementation from its inception. This arises from how stores are performed - when a store occurs, it will overwrite overlapping ranges and adjust the tree as necessary to accommodate this. A range may always ultimately span two leaf nodes. In this instance we walk the two leaf nodes, determine which elements are not overwritten to the left and to the right of the start and end of the ranges respectively and then rebalance the tree to contain these entries and the newly inserted one. This kind of store is dubbed a 'spanning store' and is implemented by mas_wr_spanning_store(). In order to reach this stage, mas_store_gfp() invokes mas_wr_preallocate(), mas_wr_store_type() and mas_wr_walk() in turn to walk the tree and update the object (mas) to traverse to the location where the write should be performed, determining its store type. When a spanning store is required, this function returns false stopping at the parent node which contains the target range, and mas_wr_store_type() marks the mas->store_type as wr_spanning_store to denote this fact. When we go to perform the store in mas_wr_spanning_store(), we first determine the elements AFTER the END of the range we wish to store (that is, to the right of the entry to be inserted) - we do this by walking to the NEXT pivot in the tree (i.e. r_mas.last + 1), starting at the node we have just determined contains the range over which we intend to write. We then turn our attention to the entries to the left of the entry we are inserting, whose state is represented by l_mas, and copy these into a 'big node', which is a special node which contains enough slots to contain two leaf node's worth of data. We then copy the entry we wish to store immediately after this - the copy and the insertion of the new entry is performed by mas_store_b_node(). After this we copy the elements to the right of the end of the range which we are inserting, if we have not exceeded the length of the node (i.e. r_mas.offset <= r_mas.end). Herein lies the bug - under very specific circumstances, this logic can break and corrupt the maple tree. Consider the following tree: Height 0 Root Node / \ pivot = 0xffff / \ pivot = ULONG_MAX / ---truncated---

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:H/I:H/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.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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-2855IBM DataPower Gateway: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um beliebigen Programmcode auszuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand zu verursachen oder andere, nicht spezifizierte Angriffe durchzuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-3376Linux Kernel: Mehrere Schwachstellen ermöglichen nicht spezifizierten Angriff

Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen und einen Denial-of-Service-Zustand zu erzeugen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20241113Security Bulletin 13 Nov 2024

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

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

d?id=CVE-2024-50163 Référence CVE CVE-2024-50164 https://www.cve.org/CVERecord?id=CVE-2024-50164 Référence CVE CVE-2024-50165 https://www.cve.org/CVERecord?id=CVE-2024-50165 Référence CVE CVE-2024-50169 https://www.cve.org/CVERecord?id=CVE-2024-50169 Référence CVE CVE-2024-50172 https://www.cve.org/CVERecord?id=CVE-2024-50172 Référence CVE CVE-2024-50182 https://www.cve.org/CVERecord?id=CVE-2024-50182 Référence CVE CVE-2024-50186 https://www.cve.org/CVERecord?id=CVE-2024-50186 Référence CVE CVE-2024-50189 https://www.cve.org/CVERecord?id=CVE-2024-50189 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50223 https://www.cve.org/CVERecord?id=CVE-2024-50223 Référence CVE CVE-2024-50226 https://www.cve.org/CVERecord?id=CVE-2024-50226 Référence CVE CVE-2024-50235 https://www.cve.org/CVERecord?id=CVE-2024-50235 Référence CVE CVE-2024-50250 https://www.cve.org/CVERecord?id=CVE-2024-50250 Référence CVE CVE-2024-50252 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50203 https://www.cve.org/CVERecord?id=CVE-2024-50203 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50206 https://www.cve.org/CVERecord?id=CVE-2024-50206 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=CVE-2024-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50203 https://www.cve.org/CVERecord?id=CVE-2024-50203 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50206 https://www.cve.org/CVERecord?id=CVE-2024-50206 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=CVE-2024-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=CVE-2024-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=CVE-2024-50209 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=CVE-2024-50218 Référence CVE CVE-2024-50229 https://www.cve.org/CVERecord?id=CVE-2024-50229 Référence CVE CVE-2024-50230 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50203 https://www.cve.org/CVERecord?id=CVE-2024-50203 Référence CVE CVE-2024-50204 https://www.cve.org/CVERecord?id=CVE-2024-50204 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50206 https://www.cve.org/CVERecord?id=CVE-2024-50206 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50197 https://www.cve.org/CVERecord?id=CVE-2024-50197 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50203 https://www.cve.org/CVERecord?id=CVE-2024-50203 Référence CVE CVE-2024-50204 https://www.cve.org/CVERecord?id=CVE-2024-50204 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50206 https://www.cve.org/CVERecord?id=CVE-2024-50206 Référence CVE CVE-2024-50207 https://www.cve.org/CVERecord?id=CVE-2024-50207 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-50189 Référence CVE CVE-2024-50191 https://www.cve.org/CVERecord?id=CVE-2024-50191 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50193 https://www.cve.org/CVERecord?id=CVE-2024-50193 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50199 https://www.cve.org/CVERecord?id=CVE-2024-50199 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50202 https://www.cve.org/CVERecord?id=CVE-2024-50202 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=CVE-2024-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=CVE-2024-50209 Référence CVE CVE-2024-50210 https://www.cve.org/CVERecord?id=CVE-2024-50210 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50218 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-50186 Référence CVE CVE-2024-50187 https://www.cve.org/CVERecord?id=CVE-2024-50187 Référence CVE CVE-2024-50188 https://www.cve.org/CVERecord?id=CVE-2024-50188 Référence CVE CVE-2024-50189 https://www.cve.org/CVERecord?id=CVE-2024-50189 Référence CVE CVE-2024-50192 https://www.cve.org/CVERecord?id=CVE-2024-50192 Référence CVE CVE-2024-50194 https://www.cve.org/CVERecord?id=CVE-2024-50194 Référence CVE CVE-2024-50195 https://www.cve.org/CVERecord?id=CVE-2024-50195 Référence CVE CVE-2024-50196 https://www.cve.org/CVERecord?id=CVE-2024-50196 Référence CVE CVE-2024-50198 https://www.cve.org/CVERecord?id=CVE-2024-50198 Référence CVE CVE-2024-50200 https://www.cve.org/CVERecord?id=CVE-2024-50200 Référence CVE CVE-2024-50201 https://www.cve.org/CVERecord?id=CVE-2024-50201 Référence CVE CVE-2024-50205 https://www.cve.org/CVERecord?id=CVE-2024-50205 Référence CVE CVE-2024-50208 https://www.cve.org/CVERecord?id=CVE-2024-50208 Référence CVE CVE-2024-50209 https://www.cve.org/CVERecord?id=CVE-2024-50209 Référence CVE CVE-2024-50210 https://www.cve.org/CVERecord?id=CVE-2024-50210 Référence CVE CVE-2024-50215 https://www.cve.org/CVERecord?id=CVE-2024-50215 Référence CVE CVE-2024-50216 https://www.cve.org/CVERecord?id=CVE-2024-50216 Référence CVE CVE-2024-50218 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028901Linux の 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
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 8 Nov 2024 · Last source change 5 Aug 2026, 11:42 UTC · CWE not yet assigned

CVE recordCVE.org · 5.2
CVSS sourceCNA
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-44702
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceUnavailable
NVD statusNVD modified after enrichment

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-44702↗Vendor CSAF · Red Hat Product Security↗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-50200 · cve.blacktree.nl