<?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>Thu, 01 Oct 2026 10:46:33 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46318 — Revert "mm/hugetlbfs: update hugetlbfs to use mmap_prepare"</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46318</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;Revert &amp;#34;mm/hugetlbfs: update hugetlbfs to use mmap_prepare&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit ea52cb24cd3f (&amp;#34;mm/hugetlbfs: update hugetlbfs to use
mmap_prepare&amp;#34;) with conflict resolution to account for changes in commit
ea52cb24cd3f (&amp;#34;mm/hugetlbfs: update hugetlbfs to use mmap_prepare&amp;#34;).&lt;/p&gt;
&lt;p&gt;The patch incorrectly handled hugetlb VMA lock allocation at the
mmap_prepare stage, where a failed allocation occurring after mmap_prepare
is called might result in the lock leaking.&lt;/p&gt;
&lt;p&gt;There is no risk of a merge causing a similar issues, as
VMA_DONTEXPAND_BIT is set for hugetlb mappings.&lt;/p&gt;
&lt;p&gt;As a first step in addressing this issue, simply revert the change so we
can rework how we do this having corrected the underlying issues.&lt;/p&gt;
&lt;p&gt;We maintain the VMA flags changes as best we can, accounting for the fact
that we were working with a VMA descriptor previously and propagating
like-for-like changes for this.&lt;/p&gt;
&lt;p&gt;Note that we invoke vma_set_flags() and do not call vma_start_write() as
vm_flags_set() does.  This is OK as it&amp;#39;s being done in an .mmap hook where
the VMA is not yet linked into the tree so nobody else can be accessing
it.&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;Revert &amp;#34;mm/hugetlbfs: update hugetlbfs to use mmap_prepare&amp;#34;&lt;/p&gt;
&lt;p&gt;This reverts commit ea52cb24cd3f (&amp;#34;mm/hugetlbfs: update hugetlbfs to use
mmap_prepare&amp;#34;) with conflict resolution to account for changes in commit
ea52cb24cd3f (&amp;#34;mm/hugetlbfs: update hugetlbfs to use mmap_prepare&amp;#34;).&lt;/p&gt;
&lt;p&gt;The patch incorrectly handled hugetlb VMA lock allocation at the
mmap_prepare stage, where a failed allocation occurring after mmap_prepare
is called might result in the lock leaking.&lt;/p&gt;
&lt;p&gt;There is no risk of a merge causing a similar issues, as
VMA_DONTEXPAND_BIT is set for hugetlb mappings.&lt;/p&gt;
&lt;p&gt;As a first step in addressing this issue, simply revert the change so we
can rework how we do this having corrected the underlying issues.&lt;/p&gt;
&lt;p&gt;We maintain the VMA flags changes as best we can, accounting for the fact
that we were working with a VMA descriptor previously and propagating
like-for-like changes for this.&lt;/p&gt;
&lt;p&gt;Note that we invoke vma_set_flags() and do not call vma_start_write() as
vm_flags_set() does.  This is OK as it&amp;#39;s being done in an .mmap hook where
the VMA is not yet linked into the tree so nobody else can be accessing
it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46318</guid>
    </item>
  </channel>
</rss>
