<?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>Mon, 28 Sep 2026 23:34:04 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50263 — fork: only invoke khugepaged, ksm hooks if no error</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50263</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;fork: only invoke khugepaged, ksm hooks if no error&lt;/p&gt;
&lt;p&gt;There is no reason to invoke these hooks early against an mm that is in an
incomplete state.&lt;/p&gt;
&lt;p&gt;The change in commit d24062914837 (&amp;#34;fork: use __mt_dup() to duplicate
maple tree in dup_mmap()&amp;#34;) makes this more pertinent as we may be in a
state where entries in the maple tree are not yet consistent.&lt;/p&gt;
&lt;p&gt;Their placement early in dup_mmap() only appears to have been meaningful
for early error checking, and since functionally it&amp;#39;d require a very small
allocation to fail (in practice &amp;#39;too small to fail&amp;#39;) that&amp;#39;d only occur in
the most dire circumstances, meaning the fork would fail or be OOM&amp;#39;d in
any case.&lt;/p&gt;
&lt;p&gt;Since both khugepaged and KSM tracking are there to provide optimisations
to memory performance rather than critical functionality, it doesn&amp;#39;t
really matter all that much if, under such dire memory pressure, we fail
to register an mm with these.&lt;/p&gt;
&lt;p&gt;As a result, we follow the example of commit d2081b2bf819 (&amp;#34;mm:
khugepaged: make khugepaged_enter() void function&amp;#34;) and make ksm_fork() a
void function also.&lt;/p&gt;
&lt;p&gt;We only expose the mm to these functions once we are done with them and
only if no error occurred in the fork operation.&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;fork: only invoke khugepaged, ksm hooks if no error&lt;/p&gt;
&lt;p&gt;There is no reason to invoke these hooks early against an mm that is in an
incomplete state.&lt;/p&gt;
&lt;p&gt;The change in commit d24062914837 (&amp;#34;fork: use __mt_dup() to duplicate
maple tree in dup_mmap()&amp;#34;) makes this more pertinent as we may be in a
state where entries in the maple tree are not yet consistent.&lt;/p&gt;
&lt;p&gt;Their placement early in dup_mmap() only appears to have been meaningful
for early error checking, and since functionally it&amp;#39;d require a very small
allocation to fail (in practice &amp;#39;too small to fail&amp;#39;) that&amp;#39;d only occur in
the most dire circumstances, meaning the fork would fail or be OOM&amp;#39;d in
any case.&lt;/p&gt;
&lt;p&gt;Since both khugepaged and KSM tracking are there to provide optimisations
to memory performance rather than critical functionality, it doesn&amp;#39;t
really matter all that much if, under such dire memory pressure, we fail
to register an mm with these.&lt;/p&gt;
&lt;p&gt;As a result, we follow the example of commit d2081b2bf819 (&amp;#34;mm:
khugepaged: make khugepaged_enter() void function&amp;#34;) and make ksm_fork() a
void function also.&lt;/p&gt;
&lt;p&gt;We only expose the mm to these functions once we are done with them and
only if no error occurred in the fork operation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50263</guid>
    </item>
  </channel>
</rss>
