<?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-09-29T14:46:55.012392+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-2023-52925</id>
    <title>CVE-2023-52925 — netfilter: nf_tables: don't fail inserts if duplicate has expired</title>
    <updated>2026-09-29T14:46:55.036207+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: nf_tables: don't fail inserts if duplicate has expired</p>
<p>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</p>
<p>Insertion must ignore duplicate but expired entries.</p>
<p>Moreover, there is a strange asymmetry in nft_pipapo_activate:</p>
<p>It refetches the current element, whereas the other -&gt;activate callbacks
(bitmap, hash, rhash, rbtree) use elem-&gt;priv.
Same for .remove: other set implementations take elem-&gt;priv,
nft_pipapo_remove fetches elem-&gt;priv, then does a relookup,
remove this.</p>
<p>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.</p>
<p>In first two cases expired elements must be skipped.</p>
<p>For -&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.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-52925"/>
  </entry>
</feed>
