<?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>Mon, 28 Sep 2026 21:30:27 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71080 — ipv6: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71080</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: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the
current task can be preempted. Another task running on the same CPU
may then execute rt6_make_pcpu_route() and successfully install a
pcpu_rt entry. When the first task resumes execution, its cmpxchg()
in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer
NULL, triggering the BUG_ON(prev). It&amp;#39;s easy to reproduce it by adding
mdelay() after rt6_get_pcpu_route().&lt;/p&gt;
&lt;p&gt;Using preempt_disable/enable is not appropriate here because
ip6_rt_pcpu_alloc() may sleep.&lt;/p&gt;
&lt;p&gt;Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT:
free our allocation and return the existing pcpu_rt installed by
another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT
kernels where such races should not occur.&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: fix a BUG in rt6_get_pcpu_route() under PREEMPT_RT&lt;/p&gt;
&lt;p&gt;On PREEMPT_RT kernels, after rt6_get_pcpu_route() returns NULL, the
current task can be preempted. Another task running on the same CPU
may then execute rt6_make_pcpu_route() and successfully install a
pcpu_rt entry. When the first task resumes execution, its cmpxchg()
in rt6_make_pcpu_route() will fail because rt6i_pcpu is no longer
NULL, triggering the BUG_ON(prev). It&amp;#39;s easy to reproduce it by adding
mdelay() after rt6_get_pcpu_route().&lt;/p&gt;
&lt;p&gt;Using preempt_disable/enable is not appropriate here because
ip6_rt_pcpu_alloc() may sleep.&lt;/p&gt;
&lt;p&gt;Fix this by handling the cmpxchg() failure gracefully on PREEMPT_RT:
free our allocation and return the existing pcpu_rt installed by
another task. The BUG_ON is replaced by WARN_ON_ONCE for non-PREEMPT_RT
kernels where such races should not occur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71080</guid>
    </item>
  </channel>
</rss>
