CVE-2024-36000: mm/hugetlb: fix missing hugetlb_lock for resv uncharge
In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix missing hugetlblock for resv uncharge
The Linux kernel CVE team has assigned CVE-2024-36000 to this issue.
Upstream advisory: https://lore.kernel.org/linux-cve-announce/2024052023-CVE-2024-36000-cfc4@gregkh/T
Other sources
In the Linux kernel, the following vulnerability has been resolved:
mm/hugetlb: fix missing hugetlblock for resv uncharge
There is a recent report on UFFDIOCOPY over hugetlb:
https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/
350: lockdepassertheld(&hugetlblock);
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: hugetlbcgroupunchargefoliorsvd() will update the cgroup pointer, so it requires to be called with the lock held.
— NVD
Linux Kernel is vulnerable to a denial of service, caused by an error related to missing hugetlblock for resv uncharge. By sending a specially crafted request, a local authenticated attacker could exploit this vulnerability to cause a denial of service.
— IBM
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2024-36000?
CVE-2024-36000 is classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2024-36000?
To mitigate CVE-2024-36000, upgrade your Linux kernel to the specified remedied versions, such as 6.1.91 or 6.6.30.
What versions of the Linux kernel are affected by CVE-2024-36000?
CVE-2024-36000 affects multiple versions of the Linux kernel, specifically versions below 6.1.91 and several versions under 6.12.
Is CVE-2024-36000 present in Debian and RedHat distributions?
Yes, CVE-2024-36000 affects both Debian and RedHat distributions of the Linux kernel.
What is the impact of CVE-2024-36000?
The impact of CVE-2024-36000 is associated with potential denial of service due to improper locking in hugetlb handling.