<?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>Sat, 03 Oct 2026 08:42:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-72252</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-72252</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: linux-lts, Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-72252</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1163 — De multiples vulnérabilités ont été découvertes dans le noyau Linux de Debian LTS. Certaines d'entre elles permettent à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</link>
      <description>certfr-2026-avi-1163</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-1163</guid>
    </item>
    <item>
      <title>EUVD-2026-357899</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357899</link>
      <description>EUVD-2026-357899</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357899</guid>
    </item>
    <item>
      <title>fkie_cve-2026-72252</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-72252</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction&lt;/p&gt;
&lt;p&gt;On memory allocation failure the cloned nft_pipapo_match can enter a bad
state:
 - some fields can have their lookup tables resized while others did
   not
 - bits might have been toggled
 - scratch map can be undersized which also means m-&amp;gt;bsize_max can be
   lower than what is required&lt;/p&gt;
&lt;p&gt;This means that the next insertion in the same batch can trigger
out-of-bounds writes.&lt;/p&gt;
&lt;p&gt;Furthermore, a failure in the first can result in the bad clone to
leak into the next transaction because the abort callback is never
executed in this case (the upper layer saw an error and no attempt to
allocate a transactional request was made).&lt;/p&gt;
&lt;p&gt;Record a state for the nft_pipapo_match structure:
- NEW (pristine clone)
- MOD (modified clone with good state)
- ERR (potentially bogus content)&lt;/p&gt;
&lt;p&gt;Then make it so that deletes and insertions fail when the clone
entered ERR state.&lt;/p&gt;
&lt;p&gt;In case the very first insert attempt results in an error, free the
clone right away.&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;netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction&lt;/p&gt;
&lt;p&gt;On memory allocation failure the cloned nft_pipapo_match can enter a bad
state:
 - some fields can have their lookup tables resized while others did
   not
 - bits might have been toggled
 - scratch map can be undersized which also means m-&amp;gt;bsize_max can be
   lower than what is required&lt;/p&gt;
&lt;p&gt;This means that the next insertion in the same batch can trigger
out-of-bounds writes.&lt;/p&gt;
&lt;p&gt;Furthermore, a failure in the first can result in the bad clone to
leak into the next transaction because the abort callback is never
executed in this case (the upper layer saw an error and no attempt to
allocate a transactional request was made).&lt;/p&gt;
&lt;p&gt;Record a state for the nft_pipapo_match structure:
- NEW (pristine clone)
- MOD (modified clone with good state)
- ERR (potentially bogus content)&lt;/p&gt;
&lt;p&gt;Then make it so that deletes and insertions fail when the clone
entered ERR state.&lt;/p&gt;
&lt;p&gt;In case the very first insert attempt results in an error, free the
clone right away.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-72252</guid>
    </item>
    <item>
      <title>GHSA-wp7x-h4hq-8jpw</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-wp7x-h4hq-8jpw</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction&lt;/p&gt;
&lt;p&gt;On memory allocation failure the cloned nft_pipapo_match can enter a bad
state:
 - some fields can have their lookup tables resized while others did
   not
 - bits might have been toggled
 - scratch map can be undersized which also means m-&amp;gt;bsize_max can be
   lower than what is required&lt;/p&gt;
&lt;p&gt;This means that the next insertion in the same batch can trigger
out-of-bounds writes.&lt;/p&gt;
&lt;p&gt;Furthermore, a failure in the first can result in the bad clone to
leak into the next transaction because the abort callback is never
executed in this case (the upper layer saw an error and no attempt to
allocate a transactional request was made).&lt;/p&gt;
&lt;p&gt;Record a state for the nft_pipapo_match structure:
- NEW (pristine clone)
- MOD (modified clone with good state)
- ERR (potentially bogus content)&lt;/p&gt;
&lt;p&gt;Then make it so that deletes and insertions fail when the clone
entered ERR state.&lt;/p&gt;
&lt;p&gt;In case the very first insert attempt results in an error, free the
clone right away.&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;netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction&lt;/p&gt;
&lt;p&gt;On memory allocation failure the cloned nft_pipapo_match can enter a bad
state:
 - some fields can have their lookup tables resized while others did
   not
 - bits might have been toggled
 - scratch map can be undersized which also means m-&amp;gt;bsize_max can be
   lower than what is required&lt;/p&gt;
&lt;p&gt;This means that the next insertion in the same batch can trigger
out-of-bounds writes.&lt;/p&gt;
&lt;p&gt;Furthermore, a failure in the first can result in the bad clone to
leak into the next transaction because the abort callback is never
executed in this case (the upper layer saw an error and no attempt to
allocate a transactional request was made).&lt;/p&gt;
&lt;p&gt;Record a state for the nft_pipapo_match structure:
- NEW (pristine clone)
- MOD (modified clone with good state)
- ERR (potentially bogus content)&lt;/p&gt;
&lt;p&gt;Then make it so that deletes and insertions fail when the clone
entered ERR state.&lt;/p&gt;
&lt;p&gt;In case the very first insert attempt results in an error, free the
clone right away.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-wp7x-h4hq-8jpw</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-72252</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72252</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 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction On memory allocation failure the cloned nft_pipapo_match can enter a bad state:  - some fields can have their lookup tables resized while others did    not  - bits might have been toggled  - scratch map can be undersized which also means m-&amp;gt;bsize_max can be    lower than what is required This means that the next insertion in the same batch can trigger out-of-bounds writes. Furthermore, a failure in the first can result in the bad clone to leak into the next transaction because the abort callback is never executed in this case (the upper layer saw an error and no attempt to allocate a transactional request was made). Record a state for the nft_pipapo_match structure: - NEW (pristine clone) - MOD (modified clone with good state) - ERR (potentially bogus content) Then make it so that deletes and insertions fail when the clone entered ERR state. In case the very first insert attempt results in an error, free the clone right away.&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 194 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: don&amp;#39;t leak bad clone into future transaction On memory allocation failure the cloned nft_pipapo_match can enter a bad state:  - some fields can have their lookup tables resized while others did    not  - bits might have been toggled  - scratch map can be undersized which also means m-&amp;gt;bsize_max can be    lower than what is required This means that the next insertion in the same batch can trigger out-of-bounds writes. Furthermore, a failure in the first can result in the bad clone to leak into the next transaction because the abort callback is never executed in this case (the upper layer saw an error and no attempt to allocate a transactional request was made). Record a state for the nft_pipapo_match structure: - NEW (pristine clone) - MOD (modified clone with good state) - ERR (potentially bogus content) Then make it so that deletes and insertions fail when the clone entered ERR state. In case the very first insert attempt results in an error, free the clone right away.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-72252</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2852 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um root Rechte zu erlangen, um einen Denial of Service herbeizuführen oder einen nicht näher spezifizierten Angriff durchzuführen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2852</guid>
    </item>
  </channel>
</rss>
