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

mm/hugetlb: fix missing hugetlb_lock for resv uncharge

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 13 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.22% 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 13 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.

17 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 13 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.8.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.94-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.8.9-1Debian Security Tracker ↗Source updated 6 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-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-36000 · CSAF 2.0 · revision 102 · interimSUSE Product Security TeamCVE-2024-36000
123 known affected

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

  • kernel-default as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-source as component of SUSE Linux Enterprise High Availability Extension 16.0
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • reiserfs-kmp-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS
Summary
In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/ 350: lockdep_assert_held(&hugetlb_lock); Should be an issue in hugetlb but triggered in an userfault context, where it goes into the unlikely path where two threads modifying the resv map together. Mike has a fix in that path for resv uncharge but it looks like the locking criteria was overlooked: hugetlb_cgroup_uncharge_folio_rsvd() will update the cgroup pointer, so it requires to be called with the lock held.
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-36109

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 13 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: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/ 350: lockdep_assert_held(&hugetlb_lock); Should be an issue in hugetlb but triggered in an userfault context, where it goes into the unlikely path where two threads modifying the resv map together. Mike has a fix in that path for resv uncharge but it looks like the locking criteria was overlooked: hugetlb_cgroup_uncharge_folio_rsvd() will update the cgroup pointer, so it requires to be called with the lock held.

What

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/ 350: lockdep_assert_held(&hugetlb_lock); Should be an issue in hugetlb but triggered in an userfault context, where it goes into the unlikely path where two threads modifying the resv map together. Mike has a fix in that path for resv uncharge but it looks like the locking criteria was overlooked: hugetlb_cgroup_uncharge_folio_rsvd() will update the cgroup pointer, so it requires to be called with the lock held.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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: mm/hugetlb: fix missing hugetlb_lock for resv uncharge There is a recent report on UFFDIO_COPY over hugetlb: https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/ 350: lockdep_assert_held(&hugetlb_lock); Should be an issue in hugetlb but triggered in an userfault context, where it goes into the unlikely path where two threads modifying the resv map together. Mike has a fix in that path for resv uncharge but it looks like the locking criteria was overlooked: hugetlb_cgroup_uncharge_folio_rsvd() will update the cgroup pointer, so it requires to be called with the lock held.

Why

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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 → Reachable Assertion → 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-617 ↗

CWE-617: Reachable Assertion. The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

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-617
A

Official authority intelligence

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

BSI · German · WID-SEC-2025-1293IBM DataPower Gateway: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM DataPower Gateway ausnutzen, um seine Privilegien zu erhöhen, Informationen auszuspähen, einen Denial-of-Service auszulösen oder weitere unspezifizierte Auswirkungen zu erzielen.

Official advisory ↗
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-2024-1188Linux 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.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20240522Security Bulletin 22 May 2024

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

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

d?id=CVE-2024-35944 Référence CVE CVE-2024-35946 https://www.cve.org/CVERecord?id=CVE-2024-35946 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35952 https://www.cve.org/CVERecord?id=CVE-2024-35952 Référence CVE CVE-2024-35958 https://www.cve.org/CVERecord?id=CVE-2024-35958 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35960 https://www.cve.org/CVERecord?id=CVE-2024-35960 Référence CVE CVE-2024-35962 https://www.cve.org/CVERecord?id=CVE-2024-35962 Référence CVE CVE-2024-35989 https://www.cve.org/CVERecord?id=CVE-2024-35989 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35945 Référence CVE CVE-2024-35946 https://www.cve.org/CVERecord?id=CVE-2024-35946 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35956 https://www.cve.org/CVERecord?id=CVE-2024-35956 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35945 Référence CVE CVE-2024-35946 https://www.cve.org/CVERecord?id=CVE-2024-35946 Référence CVE CVE-2024-35949 https://www.cve.org/CVERecord?id=CVE-2024-35949 Référence CVE CVE-2024-35956 https://www.cve.org/CVERecord?id=CVE-2024-35956 Référence CVE CVE-2024-35959 https://www.cve.org/CVERecord?id=CVE-2024-35959 Référence CVE CVE-2024-35971 https://www.cve.org/CVERecord?id=CVE-2024-35971 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=CVE-2024-36009 Référence CVE CVE-2024-36012 https://www.cve.org/CVERecord?id=CVE-2024-36012 Référence CVE CVE-2024-36013 https://www.cve.org/CVERecord?id=CVE-2024-36013 Référence CVE CVE-2024-36021 https://www.cve.org/CVERecord?id=CVE-2024-36021 Référence CVE CVE-2024-36024 https://www.cve.org/CVERecord?id=CVE-2024-36024 Référence CVE CVE-2024-36026 https://www.cve.org/CVERecord?id=CVE-2024-36026 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36331 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-27011 Référence CVE CVE-2024-27019 https://www.cve.org/CVERecord?id=CVE-2024-27019 Référence CVE CVE-2024-28863 https://www.cve.org/CVERecord?id=CVE-2024-28863 Référence CVE CVE-2024-29025 https://www.cve.org/CVERecord?id=CVE-2024-29025 Référence CVE CVE-2024-34155 https://www.cve.org/CVERecord?id=CVE-2024-34155 Référence CVE CVE-2024-34156 https://www.cve.org/CVERecord?id=CVE-2024-34156 Référence CVE CVE-2024-34158 https://www.cve.org/CVERecord?id=CVE-2024-34158 Référence CVE CVE-2024-35809 https://www.cve.org/CVERecord?id=CVE-2024-35809 Référence CVE CVE-2024-35944 https://www.cve.org/CVERecord?id=CVE-2024-35944 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36889 https://www.cve.org/CVERecord?id=CVE-2024-36889 Référence CVE CVE-2024-37890 https://www.cve.org/CVERecord?id=CVE-2024-37890 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=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0018Multiples vulnérabilités dans les produits Juniper Networks

d?id=CVE-2024-26720 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-26946 https://www.cve.org/CVERecord?id=CVE-2024-26946 Référence CVE CVE-2024-28834 https://www.cve.org/CVERecord?id=CVE-2024-28834 Référence CVE CVE-2024-28835 https://www.cve.org/CVERecord?id=CVE-2024-28835 Référence CVE CVE-2024-32462 https://www.cve.org/CVERecord?id=CVE-2024-32462 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35797 https://www.cve.org/CVERecord?id=CVE-2024-35797 Référence CVE CVE-2024-35875 https://www.cve.org/CVERecord?id=CVE-2024-35875 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36019 https://www.cve.org/CVERecord?id=CVE-2024-36019 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36979 https://www.cve.org/CVERecord?id=CVE-2024-36979 Référence CVE CVE-2024-38559 https://www.cve.org/CVERecord?id=CVE-2024-38559 Référence CVE CVE-2024-38619 https://www.cve.org/CVERecord?id=CVE-2024-38619 Référence CVE CVE-2024-39894 https://www.cve.org/CVERecord?id=CVE-2024-39894 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40936 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-26953 Référence CVE CVE-2024-27017 https://www.cve.org/CVERecord?id=CVE-2024-27017 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-27051 https://www.cve.org/CVERecord?id=CVE-2024-27051 Référence CVE CVE-2024-27407 https://www.cve.org/CVERecord?id=CVE-2024-27407 Référence CVE CVE-2024-35888 https://www.cve.org/CVERecord?id=CVE-2024-35888 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-35980 https://www.cve.org/CVERecord?id=CVE-2024-35980 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36031 https://www.cve.org/CVERecord?id=CVE-2024-36031 Référence CVE CVE-2024-36244 https://www.cve.org/CVERecord?id=CVE-2024-36244 Référence CVE CVE-2024-36484 https://www.cve.org/CVERecord?id=CVE-2024-36484 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 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-36920 https://www.cve.org/CVERecord?id=CVE-2024-36920 Référence CVE CVE-2024-36927 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-35924 Référence CVE CVE-2024-35925 https://www.cve.org/CVERecord?id=CVE-2024-35925 Référence CVE CVE-2024-35930 https://www.cve.org/CVERecord?id=CVE-2024-35930 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-35938 https://www.cve.org/CVERecord?id=CVE-2024-35938 Référence CVE CVE-2024-35940 https://www.cve.org/CVERecord?id=CVE-2024-35940 Référence CVE CVE-2024-35946 https://www.cve.org/CVERecord?id=CVE-2024-35946 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35952 https://www.cve.org/CVERecord?id=CVE-2024-35952 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=CVE-2024-36020 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2023-52801 Référence CVE CVE-2024-26629 https://www.cve.org/CVERecord?id=CVE-2024-26629 Référence CVE CVE-2024-26630 https://www.cve.org/CVERecord?id=CVE-2024-26630 Référence CVE CVE-2024-26720 https://www.cve.org/CVERecord?id=CVE-2024-26720 Référence CVE CVE-2024-26886 https://www.cve.org/CVERecord?id=CVE-2024-26886 Référence CVE CVE-2024-26946 https://www.cve.org/CVERecord?id=CVE-2024-26946 Référence CVE CVE-2024-35791 https://www.cve.org/CVERecord?id=CVE-2024-35791 Référence CVE CVE-2024-35797 https://www.cve.org/CVERecord?id=CVE-2024-35797 Référence CVE CVE-2024-35875 https://www.cve.org/CVERecord?id=CVE-2024-35875 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36019 https://www.cve.org/CVERecord?id=CVE-2024-36019 Référence CVE CVE-2024-36883 https://www.cve.org/CVERecord?id=CVE-2024-36883 Référence CVE CVE-2024-36979 https://www.cve.org/CVERecord?id=CVE-2024-36979 Référence CVE CVE-2024-38559 https://www.cve.org/CVERecord?id=CVE-2024-38559 Référence CVE CVE-2024-38619 https://www.cve.org/CVERecord?id=CVE-2024-38619 Référence CVE CVE-2024-40927 https://www.cve.org/CVERecord?id=CVE-2024-40927 Référence CVE CVE-2024-40936 https://www.cve.org/CVERecord?id=CVE-2024-40936 Référence CVE CVE-2024-41040 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35986 Référence CVE CVE-2024-35989 https://www.cve.org/CVERecord?id=CVE-2024-35989 Référence CVE CVE-2024-35990 https://www.cve.org/CVERecord?id=CVE-2024-35990 Référence CVE CVE-2024-35991 https://www.cve.org/CVERecord?id=CVE-2024-35991 Référence CVE CVE-2024-35992 https://www.cve.org/CVERecord?id=CVE-2024-35992 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35997 https://www.cve.org/CVERecord?id=CVE-2024-35997 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35988 Référence CVE CVE-2024-35989 https://www.cve.org/CVERecord?id=CVE-2024-35989 Référence CVE CVE-2024-35991 https://www.cve.org/CVERecord?id=CVE-2024-35991 Référence CVE CVE-2024-35993 https://www.cve.org/CVERecord?id=CVE-2024-35993 Référence CVE CVE-2024-35994 https://www.cve.org/CVERecord?id=CVE-2024-35994 Référence CVE CVE-2024-35996 https://www.cve.org/CVERecord?id=CVE-2024-35996 Référence CVE CVE-2024-35997 https://www.cve.org/CVERecord?id=CVE-2024-35997 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36001 https://www.cve.org/CVERecord?id=CVE-2024-36001 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36009 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35852 Référence CVE CVE-2024-35897 https://www.cve.org/CVERecord?id=CVE-2024-35897 Référence CVE CVE-2024-35898 https://www.cve.org/CVERecord?id=CVE-2024-35898 Référence CVE CVE-2024-35899 https://www.cve.org/CVERecord?id=CVE-2024-35899 Référence CVE CVE-2024-35907 https://www.cve.org/CVERecord?id=CVE-2024-35907 Référence CVE CVE-2024-35910 https://www.cve.org/CVERecord?id=CVE-2024-35910 Référence CVE CVE-2024-35911 https://www.cve.org/CVERecord?id=CVE-2024-35911 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-35969 https://www.cve.org/CVERecord?id=CVE-2024-35969 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=CVE-2024-36020 Référence CVE CVE-2024-36489 https://www.cve.org/CVERecord?id=CVE-2024-36489 Référence CVE CVE-2024-36886 https://www.cve.org/CVERecord?id=CVE-2024-36886 Référence CVE CVE-2024-36903 https://www.cve.org/CVERecord?id=CVE-2024-36903 Référence CVE CVE-2024-36921 https://www.cve.org/CVERecord?id=CVE-2024-36921 Référence CVE CVE-2024-36922 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35966 Référence CVE CVE-2024-35967 https://www.cve.org/CVERecord?id=CVE-2024-35967 Référence CVE CVE-2024-35970 https://www.cve.org/CVERecord?id=CVE-2024-35970 Référence CVE CVE-2024-35976 https://www.cve.org/CVERecord?id=CVE-2024-35976 Référence CVE CVE-2024-35978 https://www.cve.org/CVERecord?id=CVE-2024-35978 Référence CVE CVE-2024-35979 https://www.cve.org/CVERecord?id=CVE-2024-35979 Référence CVE CVE-2024-35995 https://www.cve.org/CVERecord?id=CVE-2024-35995 Référence CVE CVE-2024-35997 https://www.cve.org/CVERecord?id=CVE-2024-35997 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36008 https://www.cve.org/CVERecord?id=CVE-2024-36008 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36014 https://www.cve.org/CVERecord?id=CVE-2024-36014 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=

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

d?id=CVE-2024-35990 Référence CVE CVE-2024-35991 https://www.cve.org/CVERecord?id=CVE-2024-35991 Référence CVE CVE-2024-35992 https://www.cve.org/CVERecord?id=CVE-2024-35992 Référence CVE CVE-2024-35993 https://www.cve.org/CVERecord?id=CVE-2024-35993 Référence CVE CVE-2024-35994 https://www.cve.org/CVERecord?id=CVE-2024-35994 Référence CVE CVE-2024-35996 https://www.cve.org/CVERecord?id=CVE-2024-35996 Référence CVE CVE-2024-35997 https://www.cve.org/CVERecord?id=CVE-2024-35997 Référence CVE CVE-2024-35998 https://www.cve.org/CVERecord?id=CVE-2024-35998 Référence CVE CVE-2024-35999 https://www.cve.org/CVERecord?id=CVE-2024-35999 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36001 https://www.cve.org/CVERecord?id=CVE-2024-36001 Référence CVE CVE-2024-36002 https://www.cve.org/CVERecord?id=CVE-2024-36002 Référence CVE CVE-2024-36003 https://www.cve.org/CVERecord?id=CVE-2024-36003 Référence CVE CVE-2024-36004 https://www.cve.org/CVERecord?id=CVE-2024-36004 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36007 https://www.cve.org/CVERecord?id=CVE-2024-36007 Référence CVE CVE-2024-36008 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-35924 Référence CVE CVE-2024-35925 https://www.cve.org/CVERecord?id=CVE-2024-35925 Référence CVE CVE-2024-35930 https://www.cve.org/CVERecord?id=CVE-2024-35930 Référence CVE CVE-2024-35937 https://www.cve.org/CVERecord?id=CVE-2024-35937 Référence CVE CVE-2024-35938 https://www.cve.org/CVERecord?id=CVE-2024-35938 Référence CVE CVE-2024-35946 https://www.cve.org/CVERecord?id=CVE-2024-35946 Référence CVE CVE-2024-35947 https://www.cve.org/CVERecord?id=CVE-2024-35947 Référence CVE CVE-2024-35952 https://www.cve.org/CVERecord?id=CVE-2024-35952 Référence CVE CVE-2024-35962 https://www.cve.org/CVERecord?id=CVE-2024-35962 Référence CVE CVE-2024-36000 https://www.cve.org/CVERecord?id=CVE-2024-36000 Référence CVE CVE-2024-36005 https://www.cve.org/CVERecord?id=CVE-2024-36005 Référence CVE CVE-2024-36006 https://www.cve.org/CVERecord?id=CVE-2024-36006 Référence CVE CVE-2024-36010 https://www.cve.org/CVERecord?id=CVE-2024-36010 Référence CVE CVE-2024-36016 https://www.cve.org/CVERecord?id=CVE-2024-36016 Référence CVE CVE-2024-36017 https://www.cve.org/CVERecord?id=CVE-2024-36017 Référence CVE CVE-2024-36020 https://www.cve.org/CVERecord?id=CVE-2024-36020 Référence CVE CVE-2024-36025 https://www.cve.org/CVERecord?id=CVE-2024-36025 Référence CVE CVE-2024-36270 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2024-028316Linux の 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: < 5.10, 6.1.91 ≤ 6.1.*, 6.6.30 ≤ 6.6.*, 6.8.9 ≤ 6.8.*, 6.9 ≤ *
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 20 May 2024 · Last source change 23 May 2026, 15:46 UTC · CWE-617 · Reachable Assertion

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

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-36109↗Vendor CSAF · SUSE Product Security Team↗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-36000 · cve.blacktree.nl