<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T08:45:29.910797+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2024-36000</id>
    <title>CVE-2024-36000 — mm/hugetlb: fix missing hugetlb_lock for resv uncharge</title>
    <updated>2026-10-02T08:45:29.912663+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-36000"/>
  </entry>
</feed>
