<?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>Tue, 06 Oct 2026 21:39:35 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-80956 — dm-pcache: only hand out initialized cache segments</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-80956</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;dm-pcache: only hand out initialized cache segments&lt;/p&gt;
&lt;p&gt;get_cache_segment() scans the segment map up to cache-&amp;gt;n_segs, the
physical device segment count, but cache_segs_init() only initializes
the first cache_info-&amp;gt;n_segs segments. A crafted image with
cache_info-&amp;gt;n_segs smaller than the device count leaves the remaining
pcache_cache_segment structs zeroed (segment.data == NULL), and the
allocator can hand one to cache_kset_close(), which writes through the
returned segment&amp;#39;s data pointer with no NULL check.&lt;/p&gt;
&lt;p&gt;Bound the allocator&amp;#39;s search to cache_info-&amp;gt;n_segs so only initialized
segments are ever returned. A conforming cache sets n_segs equal to the
device segment count, so this rejects nothing legitimate.&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;dm-pcache: only hand out initialized cache segments&lt;/p&gt;
&lt;p&gt;get_cache_segment() scans the segment map up to cache-&amp;gt;n_segs, the
physical device segment count, but cache_segs_init() only initializes
the first cache_info-&amp;gt;n_segs segments. A crafted image with
cache_info-&amp;gt;n_segs smaller than the device count leaves the remaining
pcache_cache_segment structs zeroed (segment.data == NULL), and the
allocator can hand one to cache_kset_close(), which writes through the
returned segment&amp;#39;s data pointer with no NULL check.&lt;/p&gt;
&lt;p&gt;Bound the allocator&amp;#39;s search to cache_info-&amp;gt;n_segs so only initialized
segments are ever returned. A conforming cache sets n_segs equal to the
device segment count, so this rejects nothing legitimate.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-80956</guid>
    </item>
  </channel>
</rss>
