<?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://vulnerability.circl.lu</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, 29 Sep 2026 18:03:52 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-52925 — netfilter: nf_tables: don't fail inserts if duplicate has expired</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-52925</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;netfilter: nf_tables: don&amp;#39;t fail inserts if duplicate has expired&lt;/p&gt;
&lt;p&gt;nftables selftests fail:
run-tests.sh testcases/sets/0044interval_overlap_0
Expected: 0-2 . 0-3, got:
W: [FAILED]     ./testcases/sets/0044interval_overlap_0: got 1&lt;/p&gt;
&lt;p&gt;Insertion must ignore duplicate but expired entries.&lt;/p&gt;
&lt;p&gt;Moreover, there is a strange asymmetry in nft_pipapo_activate:&lt;/p&gt;
&lt;p&gt;It refetches the current element, whereas the other -&amp;gt;activate callbacks
(bitmap, hash, rhash, rbtree) use elem-&amp;gt;priv.
Same for .remove: other set implementations take elem-&amp;gt;priv,
nft_pipapo_remove fetches elem-&amp;gt;priv, then does a relookup,
remove this.&lt;/p&gt;
&lt;p&gt;I suspect this was the reason for the change that prompted the
removal of the expired check in pipapo_get() in the first place,
but skipping exired elements there makes no sense to me, this helper
is used for normal get requests, insertions (duplicate check)
and deactivate callback.&lt;/p&gt;
&lt;p&gt;In first two cases expired elements must be skipped.&lt;/p&gt;
&lt;p&gt;For -&amp;gt;deactivate(), this gets called for DELSETELEM, so it
seems to me that expired elements should be skipped as well, i.e.
delete request should fail with -ENOENT error.&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;netfilter: nf_tables: don&amp;#39;t fail inserts if duplicate has expired&lt;/p&gt;
&lt;p&gt;nftables selftests fail:
run-tests.sh testcases/sets/0044interval_overlap_0
Expected: 0-2 . 0-3, got:
W: [FAILED]     ./testcases/sets/0044interval_overlap_0: got 1&lt;/p&gt;
&lt;p&gt;Insertion must ignore duplicate but expired entries.&lt;/p&gt;
&lt;p&gt;Moreover, there is a strange asymmetry in nft_pipapo_activate:&lt;/p&gt;
&lt;p&gt;It refetches the current element, whereas the other -&amp;gt;activate callbacks
(bitmap, hash, rhash, rbtree) use elem-&amp;gt;priv.
Same for .remove: other set implementations take elem-&amp;gt;priv,
nft_pipapo_remove fetches elem-&amp;gt;priv, then does a relookup,
remove this.&lt;/p&gt;
&lt;p&gt;I suspect this was the reason for the change that prompted the
removal of the expired check in pipapo_get() in the first place,
but skipping exired elements there makes no sense to me, this helper
is used for normal get requests, insertions (duplicate check)
and deactivate callback.&lt;/p&gt;
&lt;p&gt;In first two cases expired elements must be skipped.&lt;/p&gt;
&lt;p&gt;For -&amp;gt;deactivate(), this gets called for DELSETELEM, so it
seems to me that expired elements should be skipped as well, i.e.
delete request should fail with -ENOENT error.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-52925</guid>
    </item>
  </channel>
</rss>
