<?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 21:36:34 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64563 — rhashtable: clear stale iter-&gt;p on table restart</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64563</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;rhashtable: clear stale iter-&amp;gt;p on table restart&lt;/p&gt;
&lt;p&gt;rhashtable_walk_start_check() has two restart paths when resuming a walk.
When iter-&amp;gt;walker.tbl is valid, it re-validates iter-&amp;gt;p against the table
and sets iter-&amp;gt;p = NULL if the object is gone.  When iter-&amp;gt;walker.tbl is
NULL (table was freed during resize), it resets slot and skip but forgets
to clear iter-&amp;gt;p.&lt;/p&gt;
&lt;p&gt;rhashtable_walk_next() then dereferences the stale iter-&amp;gt;p, reading
freed memory.  This is a use-after-free.&lt;/p&gt;
&lt;p&gt;Any caller that does multi-fragment rhashtable walks across
walk_stop/walk_start boundaries is affected.  Concrete cases include
netlink_diag (__netlink_diag_dump in net/netlink/diag.c) and TIPC
(tipc_nl_sk_walk in net/tipc/socket.c).&lt;/p&gt;
&lt;p&gt;Crash stack (netlink_diag):
  BUG: KASAN: slab-use-after-free in rhashtable_walk_next+0x365/0x3c0
  Read of size 8 at addr ffff88801a9d2438 (freed kmalloc-2k, offset 1080)
  Call Trace:
   rhashtable_walk_next+0x365/0x3c0 (lib/rhashtable.c:1016)
   __netlink_diag_dump+0x160/0x760 (net/netlink/diag.c:122)
   netlink_diag_dump+0xc2/0x240
   netlink_dump+0x5bc/0x1270
   netlink_recvmsg+0x7a3/0x980
   sock_recvmsg+0x1bc/0x200
   __sys_recvfrom+0x1d4/0x2c0&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;rhashtable: clear stale iter-&amp;gt;p on table restart&lt;/p&gt;
&lt;p&gt;rhashtable_walk_start_check() has two restart paths when resuming a walk.
When iter-&amp;gt;walker.tbl is valid, it re-validates iter-&amp;gt;p against the table
and sets iter-&amp;gt;p = NULL if the object is gone.  When iter-&amp;gt;walker.tbl is
NULL (table was freed during resize), it resets slot and skip but forgets
to clear iter-&amp;gt;p.&lt;/p&gt;
&lt;p&gt;rhashtable_walk_next() then dereferences the stale iter-&amp;gt;p, reading
freed memory.  This is a use-after-free.&lt;/p&gt;
&lt;p&gt;Any caller that does multi-fragment rhashtable walks across
walk_stop/walk_start boundaries is affected.  Concrete cases include
netlink_diag (__netlink_diag_dump in net/netlink/diag.c) and TIPC
(tipc_nl_sk_walk in net/tipc/socket.c).&lt;/p&gt;
&lt;p&gt;Crash stack (netlink_diag):
  BUG: KASAN: slab-use-after-free in rhashtable_walk_next+0x365/0x3c0
  Read of size 8 at addr ffff88801a9d2438 (freed kmalloc-2k, offset 1080)
  Call Trace:
   rhashtable_walk_next+0x365/0x3c0 (lib/rhashtable.c:1016)
   __netlink_diag_dump+0x160/0x760 (net/netlink/diag.c:122)
   netlink_diag_dump+0xc2/0x240
   netlink_dump+0x5bc/0x1270
   netlink_recvmsg+0x7a3/0x980
   sock_recvmsg+0x1bc/0x200
   __sys_recvfrom+0x1d4/0x2c0&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64563</guid>
    </item>
  </channel>
</rss>
