CVE-2024-36000

mm/hugetlb: fix missing hugetlb_lock for resv uncharge

MEDIUM
5.5
CVSS Score
Published: May 20, 2024 at 09:48 AM UTC
Updated: June 17, 2026 at 07:35 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 5.9.75.10 ≤ v < 6.1.915.10 ≤ v < 6.6.305.10 ≤ v < 6.8.95.10 ≤ v < 6.95.10.1 ≤ v < 6.1.915.9.7 ≤ v < 5.106.2 ≤ v < 6.6.306.7 ≤ v < 6.8.95.105.10 rc35.10 rc45.10 rc55.10 rc65.10 rc75.9.76.9 rc16.9 rc26.9 rc36.9 rc46.9 rc579aa925bf239c234be8586780e482872dc4690ddf87004c0b2bdf0f1066b88795d8e6c1dfad6cea0
Vendor states this is fixed in 4c806333efea1000a2a9620926f560ad2e1ca7cc (fixed)
Vendor states this is fixed in 538faabf31e9c53d8c870d114846fda958a0de10 (fixed)
Vendor states this is fixed in b76b46902c2d0395488c8412e1116c2486cdfcb2 (fixed)
Vendor states this is fixed in f6c5d21db16a0910152ec8aa9d5a7aed72694505 (fixed)
Vendor states this is fixed in 5.10 (unaffected)
Vendor states this is fixed in 6.1.91 (unaffected)
Vendor states this is fixed in 6.6.30 (unaffected)
Vendor states this is fixed in 6.8.9 (unaffected)
Vendor states this is fixed in 6.9 (unaffected)

References (4)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/4c806333efea1000a2a9620926f560ad2e1ca7cc
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/538faabf31e9c53d8c870d114846fda958a0de10
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/b76b46902c2d0395488c8412e1116c2486cdfcb2
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/f6c5d21db16a0910152ec8aa9d5a7aed72694505

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-617

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card