dbcve.org
Linux KernelOperating system · Linux

CVE-2024-36000

MEDIUM · 5.5 CVSS v3.1 Published 2024-05-20
Fix available
A fix is available. Upgrade to 5.10 / 6.1.91 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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/[email protected]/ 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-617

Attacker-controllable input can reach an assertion that aborts the process when it fails, so a check meant for debugging becomes a denial-of-service in production. A single crafted request takes the service down. The fix is to handle unexpected input gracefully on reachable paths rather than asserting on it.

General guidance for the reachable assertion class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Linux KernelOperating system
Affected:>= 5.9.7, < 5.10>= 5.10.1, < 6.1.91>= 6.2, < 6.6.30>= 6.7, < 6.8.9= 5.10= 6.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.10 / 6.1.91 / 6.6.30 or later
Fixed in 5.106.1.916.6.30
Vendor patch git.kernel.org →
Recommended fix High confidence

Upgrade to kernel 6.8.9 (or latest stable 6.8.x), 6.6.30 (or latest stable 6.6.x), 6.1.91 (or latest stable 6.1.x), or 5.10 depending on which branch you are on

  1. Identify the currently running kernel version using `uname -r`
  2. Check which version range your current kernel falls into (>= 5.9.7 and < 5.10, >= 5.10.1 and < 6.1.91, >= 6.2 and < 6.6.30, or >= 6.7 and < 6.8.9)
  3. Obtain and install the appropriate fixed kernel version for your distribution: For 5.9.x/5.10.x branch: upgrade to 5.10, For 5.10.x/6.1.x branch: upgrade to 6.1.91 or later, For 6.2.x/6.6.x branch: upgrade to 6.6.30 or later, For 6.7.x/6.8.x branch: upgrade to 6.8.9 or later
  4. Reboot the system to load the patched kernel
  5. Verify the fix is applied by checking the kernel version and confirming the commit 4c806333efea1000a2a9620926f560ad2e1ca7cc is included
Caveat Kernel upgrades may require rebuilding third-party kernel modules; ensure compatibility with your system before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36000 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36000 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data