https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 08:45:30 +0000 https://vulnerability.circl.lu/vuln/cve-2024-36000 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb: fix missing hugetlb_lock for resv uncharge</p> <p>There is a recent report on UFFDIO_COPY over hugetlb:</p> <p>https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/</p> <p>350: lockdep_assert_held(&amp;hugetlb_lock);</p> <p>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.</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/hugetlb: fix missing hugetlb_lock for resv uncharge</p> <p>There is a recent report on UFFDIO_COPY over hugetlb:</p> <p>https://lore.kernel.org/all/000000000000ee06de0616177560@google.com/</p> <p>350: lockdep_assert_held(&amp;hugetlb_lock);</p> <p>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.</p> https://vulnerability.circl.lu/vuln/cve-2024-36000