<?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-01T20:48:53.689952+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-2024-26809</id>
    <title>CVE-2024-26809 — netfilter: nft_set_pipapo: release elements in clone only from destroy path</title>
    <updated>2026-10-01T20:48:53.709841+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>netfilter: nft_set_pipapo: release elements in clone only from destroy path</p>
<p>Clone already always provides a current view of the lookup table, use it
to destroy the set, otherwise it is possible to destroy elements twice.</p>
<p>This fix requires:</p>
<p>212ed75dc5fb ("netfilter: nf_tables: integrate pipapo into commit protocol")</p>
<p>which came after:</p>
<p>9827a0e6e23b ("netfilter: nft_set_pipapo: release elements in clone from abort path").</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2024-26809"/>
  </entry>
</feed>
