<?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 06:55:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64069 — netfs: Fix cancellation of a DIO and single read subrequests</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64069</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 cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with 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 cancellation of a DIO and single read subrequests&lt;/p&gt;
&lt;p&gt;When the preparation of a new subrequest for a read fails, if the
subrequest has already been added to the stream-&amp;gt;subrequests list, it can&amp;#39;t
simply be put and abandoned as the collector may see it.  Also, if it
hasn&amp;#39;t been queued yet, it has two outstanding refs that both need to be
put.  Both DIO read and single-read dispatch fail at this; further, both
differ in the order they do things to the way buffered read works.&lt;/p&gt;
&lt;p&gt;Fix cancellation of both DIO-read and single-read subrequests that failed
preparation by the following steps:&lt;/p&gt;
&lt;p&gt;(1) Harmonise all three reads (buffered, dio, single) to queue the subreq
     before prepping it.&lt;/p&gt;
&lt;p&gt;(2) Make all three call netfs_queue_read() to do the queuing.&lt;/p&gt;
&lt;p&gt;(3) Set NETFS_RREQ_ALL_QUEUED independently of the queuing as we don&amp;#39;t
     know the length of the subreq at this point.&lt;/p&gt;
&lt;p&gt;(4) In all cases, set the error and NETFS_SREQ_FAILED flag on the subreq
     and then call netfs_read_subreq_terminated() to deal with it.  This
     will pass responsibility off to the collector for dealing with it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64069</guid>
    </item>
  </channel>
</rss>
