<?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 10:38:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31435 — netfs: Fix read abandonment during retry</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31435</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;netfs: Fix read abandonment during retry&lt;/p&gt;
&lt;p&gt;Under certain circumstances, all the remaining subrequests from a read
request will get abandoned during retry.  The abandonment process expects
the &amp;#39;subreq&amp;#39; variable to be set to the place to start abandonment from, but
it doesn&amp;#39;t always have a useful value (it will be uninitialised on the
first pass through the loop and it may point to a deleted subrequest on
later passes).&lt;/p&gt;
&lt;p&gt;Fix the first jump to &amp;#34;abandon:&amp;#34; to set subreq to the start of the first
subrequest expected to need retry (which, in this abandonment case, turned
out unexpectedly to no longer have NEED_RETRY set).&lt;/p&gt;
&lt;p&gt;Also clear the subreq pointer after discarding superfluous retryable
subrequests to cause an oops if we do try to access 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;netfs: Fix read abandonment during retry&lt;/p&gt;
&lt;p&gt;Under certain circumstances, all the remaining subrequests from a read
request will get abandoned during retry.  The abandonment process expects
the &amp;#39;subreq&amp;#39; variable to be set to the place to start abandonment from, but
it doesn&amp;#39;t always have a useful value (it will be uninitialised on the
first pass through the loop and it may point to a deleted subrequest on
later passes).&lt;/p&gt;
&lt;p&gt;Fix the first jump to &amp;#34;abandon:&amp;#34; to set subreq to the start of the first
subrequest expected to need retry (which, in this abandonment case, turned
out unexpectedly to no longer have NEED_RETRY set).&lt;/p&gt;
&lt;p&gt;Also clear the subreq pointer after discarding superfluous retryable
subrequests to cause an oops if we do try to access it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31435</guid>
    </item>
  </channel>
</rss>
