<?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, 05 Oct 2026 16:31:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39673 — ppp: fix race conditions in ppp_fill_forward_path</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39673</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: fix race conditions in ppp_fill_forward_path&lt;/p&gt;
&lt;p&gt;ppp_fill_forward_path() has two race conditions:&lt;/p&gt;
&lt;p&gt;1. The ppp-&amp;gt;channels list can change between list_empty() and
   list_first_entry(), as ppp_lock() is not held. If the only channel
   is deleted in ppp_disconnect_channel(), list_first_entry() may
   access an empty head or a freed entry, and trigger a panic.&lt;/p&gt;
&lt;p&gt;2. pch-&amp;gt;chan can be NULL. When ppp_unregister_channel() is called,
   pch-&amp;gt;chan is set to NULL before pch is removed from ppp-&amp;gt;channels.&lt;/p&gt;
&lt;p&gt;Fix these by using a lockless RCU approach:
- Use list_first_or_null_rcu() to safely test and access the first list
  entry.
- Convert list modifications on ppp-&amp;gt;channels to their RCU variants and
  add synchronize_net() after removal.
- Check for a NULL pch-&amp;gt;chan before dereferencing it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens SIMATIC CN 4100&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;ppp: fix race conditions in ppp_fill_forward_path&lt;/p&gt;
&lt;p&gt;ppp_fill_forward_path() has two race conditions:&lt;/p&gt;
&lt;p&gt;1. The ppp-&amp;gt;channels list can change between list_empty() and
   list_first_entry(), as ppp_lock() is not held. If the only channel
   is deleted in ppp_disconnect_channel(), list_first_entry() may
   access an empty head or a freed entry, and trigger a panic.&lt;/p&gt;
&lt;p&gt;2. pch-&amp;gt;chan can be NULL. When ppp_unregister_channel() is called,
   pch-&amp;gt;chan is set to NULL before pch is removed from ppp-&amp;gt;channels.&lt;/p&gt;
&lt;p&gt;Fix these by using a lockless RCU approach:
- Use list_first_or_null_rcu() to safely test and access the first list
  entry.
- Convert list modifications on ppp-&amp;gt;channels to their RCU variants and
  add synchronize_net() after removal.
- Check for a NULL pch-&amp;gt;chan before dereferencing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39673</guid>
    </item>
  </channel>
</rss>
