<?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>Sun, 04 Oct 2026 10:10:16 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80955</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80955</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80955</guid>
    </item>
    <item>
      <title>EUVD-2026-367254</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-367254</link>
      <description>EUVD-2026-367254</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-367254</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80955</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80955</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-pcache: fix use-after-free and invalid seg operations in kset_replay()&lt;/p&gt;
&lt;p&gt;In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt;
key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then
key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get().
This is a use-after-free on the freed key memory. Although mempool
recycled memory is not immediately reclaimed or overwritten in practice,
this is still a potential UAF bug.&lt;/p&gt;
&lt;p&gt;Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit
and calling cache_seg_get() is unreasonable since the corresponding
segment data is no longer valid.&lt;/p&gt;
&lt;p&gt;Fix both issues by moving cache_seg_get() and __set_bit() after the
gen check, so they only execute for valid keys, and using continue to
skip invalid keys.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-pcache: fix use-after-free and invalid seg operations in kset_replay()&lt;/p&gt;
&lt;p&gt;In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt;
key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then
key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get().
This is a use-after-free on the freed key memory. Although mempool
recycled memory is not immediately reclaimed or overwritten in practice,
this is still a potential UAF bug.&lt;/p&gt;
&lt;p&gt;Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit
and calling cache_seg_get() is unreasonable since the corresponding
segment data is no longer valid.&lt;/p&gt;
&lt;p&gt;Fix both issues by moving cache_seg_get() and __set_bit() after the
gen check, so they only execute for valid keys, and using continue to
skip invalid keys.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80955</guid>
    </item>
    <item>
      <title>GHSA-vjx8-9mvv-9939</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vjx8-9mvv-9939</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-pcache: fix use-after-free and invalid seg operations in kset_replay()&lt;/p&gt;
&lt;p&gt;In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt;
key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then
key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get().
This is a use-after-free on the freed key memory. Although mempool
recycled memory is not immediately reclaimed or overwritten in practice,
this is still a potential UAF bug.&lt;/p&gt;
&lt;p&gt;Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit
and calling cache_seg_get() is unreasonable since the corresponding
segment data is no longer valid.&lt;/p&gt;
&lt;p&gt;Fix both issues by moving cache_seg_get() and __set_bit() after the
gen check, so they only execute for valid keys, and using continue to
skip invalid keys.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;dm-pcache: fix use-after-free and invalid seg operations in kset_replay()&lt;/p&gt;
&lt;p&gt;In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt;
key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then
key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get().
This is a use-after-free on the freed key memory. Although mempool
recycled memory is not immediately reclaimed or overwritten in practice,
this is still a potential UAF bug.&lt;/p&gt;
&lt;p&gt;Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit
and calling cache_seg_get() is unreasonable since the corresponding
segment data is no longer valid.&lt;/p&gt;
&lt;p&gt;Fix both issues by moving cache_seg_get() and __set_bit() after the
gen check, so they only execute for valid keys, and using continue to
skip invalid keys.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vjx8-9mvv-9939</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11805-1 — kernel-devel-7.2.6-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1</link>
      <description>&lt;p&gt;kernel-devel-7.2.6-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;kernel-devel-7.2.6-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11805-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80955</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80955</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-pcache: fix use-after-free and invalid seg operations in kset_replay() In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt; key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get(). This is a use-after-free on the freed key memory. Although mempool recycled memory is not immediately reclaimed or overwritten in practice, this is still a potential UAF bug. Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit and calling cache_seg_get() is unreasonable since the corresponding segment data is no longer valid. Fix both issues by moving cache_seg_get() and __set_bit() after the gen check, so they only execute for valid keys, and using continue to skip invalid keys.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 118 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: dm-pcache: fix use-after-free and invalid seg operations in kset_replay() In kset_replay, when key-&amp;gt;seg_gen is stale (key-&amp;gt;seg_gen &amp;lt; key-&amp;gt;cache_pos.cache_seg-&amp;gt;gen), cache_key_put(key) is called but then key-&amp;gt;cache_pos.cache_seg is accessed as the argument to cache_seg_get(). This is a use-after-free on the freed key memory. Although mempool recycled memory is not immediately reclaimed or overwritten in practice, this is still a potential UAF bug. Additionally, for expired invalid keys, setting the cache-&amp;gt;seg_map bit and calling cache_seg_get() is unreasonable since the corresponding segment data is no longer valid. Fix both issues by moving cache_seg_get() and __set_bit() after the gen check, so they only execute for valid keys, and using continue to skip invalid keys.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80955</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3321 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um Sicherheitsmaßnahmen zu umgehen, Daten oder den Systemzustand zu manipulieren, Denial-of-Service-Zustände herbeizuführen oder andere, nicht näher spezifizierte Angriffe durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3321</guid>
    </item>
  </channel>
</rss>
