Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-36000: mm/hugetlb: fix missing hugetlb_lock for resv uncharge

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.22% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 4c806333efea1000a2a9620926f560ad2e1ca7cc, 5.10, 538faabf31e9c53d8c870d114846fda958a0de10.

Low priority for now. Upgrade to Linux Linux 4c806333efea1000a2a9620926f560ad2e1ca7cc, 5.10, 538faabf31e9c53d8c870d114846fda958a0de10 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 20, 2024
Updated
Jun 17, 2026
EPSS
0.2% · 13th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-36000

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • linux linux kernel5.9.7 and later · before 5.10
  • linux linux kernel5.10.1 and later · before 6.1.91
  • linux linux kernel6.2 and later · before 6.6.30
  • linux linux kernel6.7 and later · before 6.8.9
  • linux linux kernel5.10
  • linux linux kernel6.9

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • f87004c0b2bdf0f1066b88795d8e6c1dfad6cea0, 5.10affected
    • 79aa925bf239c234be8586780e482872dc4690dd and later · before 4c806333efea1000a2a9620926f560ad2e1ca7ccaffected · git
    • 79aa925bf239c234be8586780e482872dc4690dd and later · before f6c5d21db16a0910152ec8aa9d5a7aed72694505affected · git
    • 79aa925bf239c234be8586780e482872dc4690dd and later · before 538faabf31e9c53d8c870d114846fda958a0de10affected · git
    • 79aa925bf239c234be8586780e482872dc4690dd and later · before b76b46902c2d0395488c8412e1116c2486cdfcb2affected · git
    • 5.9.7 and later · before 5.10affected · semver
    • before 5.10not affected · semver
    • 6.1.91 and later · up to and including 6.1.*not affected · semver
    • 6.6.30 and later · up to and including 6.6.*not affected · semver
    • 6.8.9 and later · up to and including 6.8.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:9bpftoolbefore 7.3.0-427.35.1.el9_47.3.0-427.35.1.el9_4
AlmaLinux:9kernelbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64kbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debugbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-develbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-cross-headersbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-debugbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-debug-corebefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-debug-develbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4
AlmaLinux:9kernel-debug-modulesbefore 5.14.0-427.35.1.el9_45.14.0-427.35.1.el9_4

+96

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-35998May 20, 2024 · smb3: fix lock ordering potential deadlock in cifs_sync_mid_result
    22Monitor
  • ← EarlierCVE-2024-35999May 20, 2024 · smb3: missing lock when picking channel
    30Monitor
  • Later →CVE-2024-36001May 20, 2024 · netfs: Fix the pre-flush when appending to a file in writethrough mode
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux4c806333efea1000a2a9620926f560ad2e1ca7ccVendor (CNA)
Linux Linux5.10Vendor (CNA)
Linux Linux538faabf31e9c53d8c870d114846fda958a0de10Vendor (CNA)
Linux Linuxb76b46902c2d0395488c8412e1116c2486cdfcb2Vendor (CNA)
Linux Linuxf6c5d21db16a0910152ec8aa9d5a7aed72694505Vendor (CNA)
almalinux:bpftool7.3.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.35.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.94-1 · Debian:12Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.20.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-rt6.4.0-150600.10.20.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:bpftool0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-372.115.1.el8_6 · Red Hat:rhel_aus:8.6::baseosPackage registry (OSV)

+16

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2023-2156377 days apartA flaw was found in the networking subsystem of the Linux kernel within the handling of the RPL protocol.
    32Monitor
  • CVE-2023-5262155 days apartbpf: Check rcu_read_lock_trace_held() before calling bpf map helpers
    31Monitor
  • CVE-2025-39803483 days apartscsi: ufs: core: Remove WARN_ON_ONCE() call from ufshcd_uic_cmd_compl()
    31Monitor
  • CVE-2024-359570 days apartiommu/vt-d: Fix WARN_ON in iommu probe path
    22Monitor
  • CVE-2021-473151 days apartmemory: fsl_ifc: fix leak of IO mapping on probe failure
    22Monitor
  • CVE-2023-528311 days apartcpu/hotplug: Don't offline the last non-isolated CPU
    22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-617 · Reachable Assertion

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records