<?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://cve.radiocsirt.org</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 06:53:32 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26630 — mm: cachestat: fix folio read-after-free in cache walk</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2024-26630</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;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&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;mm: cachestat: fix folio read-after-free in cache walk&lt;/p&gt;
&lt;p&gt;In cachestat, we access the folio from the page cache&amp;#39;s xarray to compute
its page offset, and check for its dirty and writeback flags.  However, we
do not hold a reference to the folio before performing these actions,
which means the folio can concurrently be released and reused as another
folio/page/slab.&lt;/p&gt;
&lt;p&gt;Get around this altogether by just using xarray&amp;#39;s existing machinery for
the folio page offsets and dirty/writeback states.&lt;/p&gt;
&lt;p&gt;This changes behavior for tmpfs files to now always report zeroes in their
dirty and writeback counters.  This is okay as tmpfs doesn&amp;#39;t follow
conventional writeback cache behavior: its pages get &amp;#34;cleaned&amp;#34; during
swapout, after which they&amp;#39;re no longer resident etc.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2024-26630</guid>
    </item>
  </channel>
</rss>
