<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 11:19:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-50630 — mm: hugetlb: fix UAF in hugetlb_handle_userfault</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-50630</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: hugetlb: fix UAF in hugetlb_handle_userfault&lt;/p&gt;
&lt;p&gt;The vma_lock and hugetlb_fault_mutex are dropped before handling userfault
and reacquire them again after handle_userfault(), but reacquire the
vma_lock could lead to UAF[1,2] due to the following race,&lt;/p&gt;
&lt;p&gt;hugetlb_fault
  hugetlb_no_page
    /*unlock vma_lock */
    hugetlb_handle_userfault
      handle_userfault
        /* unlock mm-&amp;gt;mmap_lock*/
                                           vm_mmap_pgoff
                                             do_mmap
                                               mmap_region
                                                 munmap_vma_range
                                                   /* clean old vma */
        /* lock vma_lock again  &amp;lt;--- UAF */
    /* unlock vma_lock */&lt;/p&gt;
&lt;p&gt;Since the vma_lock will unlock immediately after
hugetlb_handle_userfault(), let&amp;#39;s drop the unneeded lock and unlock in
hugetlb_handle_userfault() to fix the issue.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/
[2] https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm: hugetlb: fix UAF in hugetlb_handle_userfault&lt;/p&gt;
&lt;p&gt;The vma_lock and hugetlb_fault_mutex are dropped before handling userfault
and reacquire them again after handle_userfault(), but reacquire the
vma_lock could lead to UAF[1,2] due to the following race,&lt;/p&gt;
&lt;p&gt;hugetlb_fault
  hugetlb_no_page
    /*unlock vma_lock */
    hugetlb_handle_userfault
      handle_userfault
        /* unlock mm-&amp;gt;mmap_lock*/
                                           vm_mmap_pgoff
                                             do_mmap
                                               mmap_region
                                                 munmap_vma_range
                                                   /* clean old vma */
        /* lock vma_lock again  &amp;lt;--- UAF */
    /* unlock vma_lock */&lt;/p&gt;
&lt;p&gt;Since the vma_lock will unlock immediately after
hugetlb_handle_userfault(), let&amp;#39;s drop the unneeded lock and unlock in
hugetlb_handle_userfault() to fix the issue.&lt;/p&gt;
&lt;p&gt;[1] https://lore.kernel.org/linux-mm/000000000000d5e00a05e834962e@google.com/
[2] https://lore.kernel.org/linux-mm/20220921014457.1668-1-liuzixian4@huawei.com/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-50630</guid>
    </item>
  </channel>
</rss>
