<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-05T10:19:37.661407+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-80956</id>
    <title>CVE-2026-80956 — dm-pcache: only hand out initialized cache segments</title>
    <updated>2026-10-05T10:19:38.507193+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>dm-pcache: only hand out initialized cache segments</p>
<p>get_cache_segment() scans the segment map up to cache-&gt;n_segs, the
physical device segment count, but cache_segs_init() only initializes
the first cache_info-&gt;n_segs segments. A crafted image with
cache_info-&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's data pointer with no NULL check.</p>
<p>Bound the allocator's search to cache_info-&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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-80956"/>
  </entry>
</feed>
