<?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>Wed, 07 Oct 2026 19:24:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49425 — f2fs: fix dereference of stale list iterator after loop body</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2022-49425</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;f2fs: fix dereference of stale list iterator after loop body&lt;/p&gt;
&lt;p&gt;The list iterator variable will be a bogus pointer if no break was hit.
Dereferencing it (cur-&amp;gt;page in this case) could load an out-of-bounds/undefined
value making it unsafe to use that in the comparision to determine if the
specific element was found.&lt;/p&gt;
&lt;p&gt;Since &amp;#39;cur-&amp;gt;page&amp;#39; *can* be out-ouf-bounds it cannot be guaranteed that
by chance (or intention of an attacker) it matches the value of &amp;#39;page&amp;#39;
even though the correct element was not found.&lt;/p&gt;
&lt;p&gt;This is fixed by using a separate list iterator variable for the loop
and only setting the original variable if a suitable element was found.
Then determing if the element was found is simply checking if the
variable is set.&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;f2fs: fix dereference of stale list iterator after loop body&lt;/p&gt;
&lt;p&gt;The list iterator variable will be a bogus pointer if no break was hit.
Dereferencing it (cur-&amp;gt;page in this case) could load an out-of-bounds/undefined
value making it unsafe to use that in the comparision to determine if the
specific element was found.&lt;/p&gt;
&lt;p&gt;Since &amp;#39;cur-&amp;gt;page&amp;#39; *can* be out-ouf-bounds it cannot be guaranteed that
by chance (or intention of an attacker) it matches the value of &amp;#39;page&amp;#39;
even though the correct element was not found.&lt;/p&gt;
&lt;p&gt;This is fixed by using a separate list iterator variable for the loop
and only setting the original variable if a suitable element was found.
Then determing if the element was found is simply checking if the
variable is set.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2022-49425</guid>
    </item>
  </channel>
</rss>
