<?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 11:53:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-22084 — w1: fix NULL pointer dereference in probe</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-22084</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;w1: fix NULL pointer dereference in probe&lt;/p&gt;
&lt;p&gt;The w1_uart_probe() function calls w1_uart_serdev_open() (which includes
devm_serdev_device_open()) before setting the client ops via
serdev_device_set_client_ops(). This ordering can trigger a NULL pointer
dereference in the serdev controller&amp;#39;s receive_buf handler, as it assumes
serdev-&amp;gt;ops is valid when SERPORT_ACTIVE is set.&lt;/p&gt;
&lt;p&gt;This is similar to the issue fixed in commit 5e700b384ec1
(&amp;#34;platform/chrome: cros_ec_uart: properly fix race condition&amp;#34;) where
devm_serdev_device_open() was called before fully initializing the
device.&lt;/p&gt;
&lt;p&gt;Fix the race by ensuring client ops are set before enabling the port via
w1_uart_serdev_open().&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;w1: fix NULL pointer dereference in probe&lt;/p&gt;
&lt;p&gt;The w1_uart_probe() function calls w1_uart_serdev_open() (which includes
devm_serdev_device_open()) before setting the client ops via
serdev_device_set_client_ops(). This ordering can trigger a NULL pointer
dereference in the serdev controller&amp;#39;s receive_buf handler, as it assumes
serdev-&amp;gt;ops is valid when SERPORT_ACTIVE is set.&lt;/p&gt;
&lt;p&gt;This is similar to the issue fixed in commit 5e700b384ec1
(&amp;#34;platform/chrome: cros_ec_uart: properly fix race condition&amp;#34;) where
devm_serdev_device_open() was called before fully initializing the
device.&lt;/p&gt;
&lt;p&gt;Fix the race by ensuring client ops are set before enabling the port via
w1_uart_serdev_open().&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-22084</guid>
    </item>
  </channel>
</rss>
