CVE-2024-36000 Affecting kernel-debug-debuginfo package, versions <0:4.18.0-553.16.1.el8_10
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-ROCKY8-KERNELDEBUGDEBUGINFO-7785047
- published 22 Aug 2024
- disclosed 20 May 2024
Introduced: 20 May 2024
CVE-2024-36000 Open this link in a new tabHow to fix?
Upgrade Rocky-Linux:8 kernel-debug-debuginfo to version 0:4.18.0-553.16.1.el8_10 or higher.
This issue was patched in RLSA-2024:5101.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-debug-debuginfo package and not the kernel-debug-debuginfo package as distributed by Rocky-Linux.
See How to fix? for Rocky-Linux:8 relevant fixed versions and status.
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.
References
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-36000
- https://git.kernel.org/stable/c/4c806333efea1000a2a9620926f560ad2e1ca7cc
- https://git.kernel.org/stable/c/538faabf31e9c53d8c870d114846fda958a0de10
- https://git.kernel.org/stable/c/b76b46902c2d0395488c8412e1116c2486cdfcb2
- https://git.kernel.org/stable/c/f6c5d21db16a0910152ec8aa9d5a7aed72694505