<?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>Sat, 03 Oct 2026 21:34:23 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-57928 — netfs: Fix enomem handling in buffered reads</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-57928</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 enomem handling in buffered reads&lt;/p&gt;
&lt;p&gt;If netfs_read_to_pagecache() gets an error from either -&amp;gt;prepare_read() or
from netfs_prepare_read_iterator(), it needs to decrement -&amp;gt;nr_outstanding,
cancel the subrequest and break out of the issuing loop.  Currently, it
only does this for two of the cases, but there are two more that aren&amp;#39;t
handled.&lt;/p&gt;
&lt;p&gt;Fix this by moving the handling to a common place and jumping to it from
all four places.  This is in preference to inserting a wrapper around
netfs_prepare_read_iterator() as proposed by Dmitry Antipov[1].&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 enomem handling in buffered reads&lt;/p&gt;
&lt;p&gt;If netfs_read_to_pagecache() gets an error from either -&amp;gt;prepare_read() or
from netfs_prepare_read_iterator(), it needs to decrement -&amp;gt;nr_outstanding,
cancel the subrequest and break out of the issuing loop.  Currently, it
only does this for two of the cases, but there are two more that aren&amp;#39;t
handled.&lt;/p&gt;
&lt;p&gt;Fix this by moving the handling to a common place and jumping to it from
all four places.  This is in preference to inserting a wrapper around
netfs_prepare_read_iterator() as proposed by Dmitry Antipov[1].&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-57928</guid>
    </item>
  </channel>
</rss>
