<?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 07:45:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-54243 — netfilter: ebtables: fix table blob use-after-free</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-54243</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: ebtables: fix table blob use-after-free&lt;/p&gt;
&lt;p&gt;We are not allowed to return an error at this point.
Looking at the code it looks like ret is always 0 at this
point, but its not.&lt;/p&gt;
&lt;p&gt;t = find_table_lock(net, repl-&amp;gt;name, &amp;amp;ret, &amp;amp;ebt_mutex);&lt;/p&gt;
&lt;p&gt;... this can return a valid table, with ret != 0.&lt;/p&gt;
&lt;p&gt;This bug causes update of table-&amp;gt;private with the new
blob, but then frees the blob right away in the caller.&lt;/p&gt;
&lt;p&gt;Syzbot report:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in __ebt_unregister_table+0xc00/0xcd0 net/bridge/netfilter/ebtables.c:1168
Read of size 4 at addr ffffc90005425000 by task kworker/u4:4/74
Workqueue: netns cleanup_net
Call Trace:
 kasan_report+0xbf/0x1f0 mm/kasan/report.c:517
 __ebt_unregister_table+0xc00/0xcd0 net/bridge/netfilter/ebtables.c:1168
 ebt_unregister_table+0x35/0x40 net/bridge/netfilter/ebtables.c:1372
 ops_exit_list+0xb0/0x170 net/core/net_namespace.c:169
 cleanup_net+0x4ee/0xb10 net/core/net_namespace.c:613
...&lt;/p&gt;
&lt;p&gt;ip(6)tables appears to be ok (ret should be 0 at this point) but make
this more obvious.&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: ebtables: fix table blob use-after-free&lt;/p&gt;
&lt;p&gt;We are not allowed to return an error at this point.
Looking at the code it looks like ret is always 0 at this
point, but its not.&lt;/p&gt;
&lt;p&gt;t = find_table_lock(net, repl-&amp;gt;name, &amp;amp;ret, &amp;amp;ebt_mutex);&lt;/p&gt;
&lt;p&gt;... this can return a valid table, with ret != 0.&lt;/p&gt;
&lt;p&gt;This bug causes update of table-&amp;gt;private with the new
blob, but then frees the blob right away in the caller.&lt;/p&gt;
&lt;p&gt;Syzbot report:&lt;/p&gt;
&lt;p&gt;BUG: KASAN: vmalloc-out-of-bounds in __ebt_unregister_table+0xc00/0xcd0 net/bridge/netfilter/ebtables.c:1168
Read of size 4 at addr ffffc90005425000 by task kworker/u4:4/74
Workqueue: netns cleanup_net
Call Trace:
 kasan_report+0xbf/0x1f0 mm/kasan/report.c:517
 __ebt_unregister_table+0xc00/0xcd0 net/bridge/netfilter/ebtables.c:1168
 ebt_unregister_table+0x35/0x40 net/bridge/netfilter/ebtables.c:1372
 ops_exit_list+0xb0/0x170 net/core/net_namespace.c:169
 cleanup_net+0x4ee/0xb10 net/core/net_namespace.c:613
...&lt;/p&gt;
&lt;p&gt;ip(6)tables appears to be ok (ret should be 0 at this point) but make
this more obvious.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-54243</guid>
    </item>
  </channel>
</rss>
