<?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 22:16:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74398 — ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74398</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;ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD&lt;/p&gt;
&lt;p&gt;addrconf_dad_failure() transitions ifp-&amp;gt;state from DAD to POSTDAD
via addrconf_dad_end(), which drops ifp-&amp;gt;lock on return.  The lock
is re-acquired after net_info_ratelimited().  A concurrent
ipv6_del_addr() can take the lock in that window, set ifp-&amp;gt;state
to DEAD and run list_del_rcu(&amp;amp;ifp-&amp;gt;if_list).&lt;/p&gt;
&lt;p&gt;addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad:
and schedules a new dad_work.  The work calls ipv6_del_addr()
again, hitting the already-poisoned list entry:&lt;/p&gt;
&lt;p&gt;general protection fault: 0000 [#1] SMP NOPTI
  CPU: 4 PID: 217 Comm: kworker/4:1
  Workqueue: ipv6_addrconf addrconf_dad_work
  RIP: 0010:ipv6_del_addr+0xe9/0x280
  RAX: dead000000000122
  Call Trace:
   addrconf_dad_stop+0x113/0x140
   addrconf_dad_work+0x28c/0x430
   process_one_work+0x1eb/0x3b0
   worker_thread+0x4d/0x400
   kthread+0x104/0x140
   ret_from_fork+0x35/0x40&lt;/p&gt;
&lt;p&gt;Fold the addrconf_dad_end() logic into addrconf_dad_failure() under
a single ifp-&amp;gt;lock critical section.  The STABLE_PRIVACY branch
temporarily drops ifp-&amp;gt;lock around address regeneration, so at
lock_errdad: verify the state is still POSTDAD before transitioning
to ERRDAD; bail out otherwise to avoid overwriting a state set by
another path while the lock was released.&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;ipv6: addrconf: bail out of dad_failure when state is no longer POSTDAD&lt;/p&gt;
&lt;p&gt;addrconf_dad_failure() transitions ifp-&amp;gt;state from DAD to POSTDAD
via addrconf_dad_end(), which drops ifp-&amp;gt;lock on return.  The lock
is re-acquired after net_info_ratelimited().  A concurrent
ipv6_del_addr() can take the lock in that window, set ifp-&amp;gt;state
to DEAD and run list_del_rcu(&amp;amp;ifp-&amp;gt;if_list).&lt;/p&gt;
&lt;p&gt;addrconf_dad_failure() then overwrites DEAD with ERRDAD at errdad:
and schedules a new dad_work.  The work calls ipv6_del_addr()
again, hitting the already-poisoned list entry:&lt;/p&gt;
&lt;p&gt;general protection fault: 0000 [#1] SMP NOPTI
  CPU: 4 PID: 217 Comm: kworker/4:1
  Workqueue: ipv6_addrconf addrconf_dad_work
  RIP: 0010:ipv6_del_addr+0xe9/0x280
  RAX: dead000000000122
  Call Trace:
   addrconf_dad_stop+0x113/0x140
   addrconf_dad_work+0x28c/0x430
   process_one_work+0x1eb/0x3b0
   worker_thread+0x4d/0x400
   kthread+0x104/0x140
   ret_from_fork+0x35/0x40&lt;/p&gt;
&lt;p&gt;Fold the addrconf_dad_end() logic into addrconf_dad_failure() under
a single ifp-&amp;gt;lock critical section.  The STABLE_PRIVACY branch
temporarily drops ifp-&amp;gt;lock around address regeneration, so at
lock_errdad: verify the state is still POSTDAD before transitioning
to ERRDAD; bail out otherwise to avoid overwriting a state set by
another path while the lock was released.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74398</guid>
    </item>
  </channel>
</rss>
