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:06 +0000 https://vulnerability.circl.lu/vuln/cve-2026-46042 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()</p> <p>weighted_interleave_auto_store() fetches old_wi_state inside the if (!input) block only. This causes two memory leaks:</p> <p>1. When a user writes &#34;false&#34; and the current mode is already manual, the function returns early without freeing the freshly allocated new_wi_state.</p> <p>2. When a user writes &#34;true&#34;, old_wi_state stays NULL because the fetch is skipped entirely. The old state is then overwritten by rcu_assign_pointer() but never freed, since the cleanup path is gated on old_wi_state being non-NULL. A user can trigger this repeatedly by writing &#34;1&#34; in a loop.</p> <p>Fix both leaks by moving the old_wi_state fetch before the input check, making it unconditional. This also allows a unified early return for both &#34;true&#34; and &#34;false&#34; when the requested mode matches the current mode.</p> <p>Reviewed by: Donet Tom &lt;donettom@linux.ibm.com&gt;</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm/mempolicy: fix memory leaks in weighted_interleave_auto_store()</p> <p>weighted_interleave_auto_store() fetches old_wi_state inside the if (!input) block only. This causes two memory leaks:</p> <p>1. When a user writes &#34;false&#34; and the current mode is already manual, the function returns early without freeing the freshly allocated new_wi_state.</p> <p>2. When a user writes &#34;true&#34;, old_wi_state stays NULL because the fetch is skipped entirely. The old state is then overwritten by rcu_assign_pointer() but never freed, since the cleanup path is gated on old_wi_state being non-NULL. A user can trigger this repeatedly by writing &#34;1&#34; in a loop.</p> <p>Fix both leaks by moving the old_wi_state fetch before the input check, making it unconditional. This also allows a unified early return for both &#34;true&#34; and &#34;false&#34; when the requested mode matches the current mode.</p> <p>Reviewed by: Donet Tom &lt;donettom@linux.ibm.com&gt;</p> https://vulnerability.circl.lu/vuln/cve-2026-46042