<?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 02:20:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2023-53189 — ipv6/addrconf: fix a potential refcount underflow for idev</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2023-53189</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: fix a potential refcount underflow for idev&lt;/p&gt;
&lt;p&gt;Now in addrconf_mod_rs_timer(), reference idev depends on whether
rs_timer is not pending. Then modify rs_timer timeout.&lt;/p&gt;
&lt;p&gt;There is a time gap in [1], during which if the pending rs_timer
becomes not pending. It will miss to hold idev, but the rs_timer
is activated. Thus rs_timer callback function addrconf_rs_timer()
will be executed and put idev later without holding idev. A refcount
underflow issue for idev can be caused by this.&lt;/p&gt;
&lt;p&gt;if (!timer_pending(&amp;amp;idev-&amp;gt;rs_timer))
		in6_dev_hold(idev);
		  &amp;lt;--------------[1]
	mod_timer(&amp;amp;idev-&amp;gt;rs_timer, jiffies + when);&lt;/p&gt;
&lt;p&gt;To fix the issue, hold idev if mod_timer() return 0.&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: fix a potential refcount underflow for idev&lt;/p&gt;
&lt;p&gt;Now in addrconf_mod_rs_timer(), reference idev depends on whether
rs_timer is not pending. Then modify rs_timer timeout.&lt;/p&gt;
&lt;p&gt;There is a time gap in [1], during which if the pending rs_timer
becomes not pending. It will miss to hold idev, but the rs_timer
is activated. Thus rs_timer callback function addrconf_rs_timer()
will be executed and put idev later without holding idev. A refcount
underflow issue for idev can be caused by this.&lt;/p&gt;
&lt;p&gt;if (!timer_pending(&amp;amp;idev-&amp;gt;rs_timer))
		in6_dev_hold(idev);
		  &amp;lt;--------------[1]
	mod_timer(&amp;amp;idev-&amp;gt;rs_timer, jiffies + when);&lt;/p&gt;
&lt;p&gt;To fix the issue, hold idev if mod_timer() return 0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2023-53189</guid>
    </item>
  </channel>
</rss>
