<?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>Thu, 01 Oct 2026 06:48:38 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-26924 — netfilter: nft_set_pipapo: do not free live element</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-26924</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_set_pipapo: do not free live element&lt;/p&gt;
&lt;p&gt;Pablo reports a crash with large batches of elements with a
back-to-back add/remove pattern.  Quoting Pablo:&lt;/p&gt;
&lt;p&gt;add_elem(&amp;#34;00000000&amp;#34;) timeout 100 ms
  ...
  add_elem(&amp;#34;0000000X&amp;#34;) timeout 100 ms
  del_elem(&amp;#34;0000000X&amp;#34;) &amp;lt;---------------- delete one that was just added
  ...
  add_elem(&amp;#34;00005000&amp;#34;) timeout 100 ms&lt;/p&gt;
&lt;p&gt;1) nft_pipapo_remove() removes element 0000000X
  Then, KASAN shows a splat.&lt;/p&gt;
&lt;p&gt;Looking at the remove function there is a chance that we will drop a
rule that maps to a non-deactivated element.&lt;/p&gt;
&lt;p&gt;Removal happens in two steps, first we do a lookup for key k and return the
to-be-removed element and mark it as inactive in the next generation.
Then, in a second step, the element gets removed from the set/map.&lt;/p&gt;
&lt;p&gt;The _remove function does not work correctly if we have more than one
element that share the same key.&lt;/p&gt;
&lt;p&gt;This can happen if we insert an element into a set when the set already
holds an element with same key, but the element mapping to the existing
key has timed out or is not active in the next generation.&lt;/p&gt;
&lt;p&gt;In such case its possible that removal will unmap the wrong element.
If this happens, we will leak the non-deactivated element, it becomes
unreachable.&lt;/p&gt;
&lt;p&gt;The element that got deactivated (and will be freed later) will
remain reachable in the set data structure, this can result in
a crash when such an element is retrieved during lookup (stale
pointer)…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, linux_kernel&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfilter: nft_set_pipapo: do not free live element&lt;/p&gt;
&lt;p&gt;Pablo reports a crash with large batches of elements with a
back-to-back add/remove pattern.  Quoting Pablo:&lt;/p&gt;
&lt;p&gt;add_elem(&amp;#34;00000000&amp;#34;) timeout 100 ms
  ...
  add_elem(&amp;#34;0000000X&amp;#34;) timeout 100 ms
  del_elem(&amp;#34;0000000X&amp;#34;) &amp;lt;---------------- delete one that was just added
  ...
  add_elem(&amp;#34;00005000&amp;#34;) timeout 100 ms&lt;/p&gt;
&lt;p&gt;1) nft_pipapo_remove() removes element 0000000X
  Then, KASAN shows a splat.&lt;/p&gt;
&lt;p&gt;Looking at the remove function there is a chance that we will drop a
rule that maps to a non-deactivated element.&lt;/p&gt;
&lt;p&gt;Removal happens in two steps, first we do a lookup for key k and return the
to-be-removed element and mark it as inactive in the next generation.
Then, in a second step, the element gets removed from the set/map.&lt;/p&gt;
&lt;p&gt;The _remove function does not work correctly if we have more than one
element that share the same key.&lt;/p&gt;
&lt;p&gt;This can happen if we insert an element into a set when the set already
holds an element with same key, but the element mapping to the existing
key has timed out or is not active in the next generation.&lt;/p&gt;
&lt;p&gt;In such case its possible that removal will unmap the wrong element.
If this happens, we will leak the non-deactivated element, it becomes
unreachable.&lt;/p&gt;
&lt;p&gt;The element that got deactivated (and will be freed later) will
remain reachable in the set data structure, this can result in
a crash when such an element is retrieved during lookup (stale
pointer)…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-26924</guid>
    </item>
    <item>
      <title>LSN-0105-1 — Kernel Live Patch Security Notice</title>
      <link>https://vulnerability.circl.lu/vuln/lsn-0105-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15 and 29 more&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code.(CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the netfilter connection tracker for netlink in the
Linux kernel did not properly perform reference counting in some error
conditions. A local attacker could possibly use this to cause a denial of
service (memory exhaustion).(CVE-2023-7192)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: netfilter: nf_tables: disallow anonymous set with timeout flag
Anonymous sets are never used with timeout from userspace, reject this.
Exception to this rule is NFT_SET_EVAL to ensure legacy meters still work.(CVE-2024-26642)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we
step through the buffer and after each item we check if the size_left is
greater than the minimum size we need. However, the problem is that
&amp;#39;bytes_left&amp;#39; is type ssize_t while sizeof() is type size_t. That means that
because of type promotion, the comparison is done as an unsigned and if we
have negative bytes left the loop continues instead of ending.(CVE-2024-26828)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15 and 29 more&lt;/p&gt;
&lt;p&gt;It was discovered that the ATA over Ethernet (AoE) driver in the Linux
kernel contained a race condition, leading to a use-after-free
vulnerability. An attacker could use this to cause a denial of service or
possibly execute arbitrary code.(CVE-2023-6270)&lt;/p&gt;
&lt;p&gt;It was discovered that the netfilter connection tracker for netlink in the
Linux kernel did not properly perform reference counting in some error
conditions. A local attacker could possibly use this to cause a denial of
service (memory exhaustion).(CVE-2023-7192)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: netfilter: nf_tables: disallow anonymous set with timeout flag
Anonymous sets are never used with timeout from userspace, reject this.
Exception to this rule is NFT_SET_EVAL to ensure legacy meters still work.(CVE-2024-26642)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we
step through the buffer and after each item we check if the size_left is
greater than the minimum size we need. However, the problem is that
&amp;#39;bytes_left&amp;#39; is type ssize_t while sizeof() is type size_t. That means that
because of type promotion, the comparison is done as an unsigned and if we
have negative bytes left the loop continues instead of ending.(CVE-2024-26828)&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: netfilter: nft_set_pipapo: do not free live element (CVE-2024-26924)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/lsn-0105-1</guid>
    </item>
  </channel>
</rss>
