<?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 16:00:12 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31740 — counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel's dev member</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31740</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;counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel&amp;#39;s dev member&lt;/p&gt;
&lt;p&gt;The counter driver can use HW channels 1 and 2, while the PWM driver can
use HW channels 0, 1, 2, 3, 4, 6, 7.&lt;/p&gt;
&lt;p&gt;The dev member is assigned both by the counter driver and the PWM driver
for channels 1 and 2, to their own struct device instance, overwriting
the previous value.&lt;/p&gt;
&lt;p&gt;The sub-drivers race to assign their own struct device pointer to the
same struct rz_mtu3_channel&amp;#39;s dev member.&lt;/p&gt;
&lt;p&gt;The dev member of struct rz_mtu3_channel is used by the counter
sub-driver for runtime PM.&lt;/p&gt;
&lt;p&gt;Depending on the probe order of the counter and PWM sub-drivers, the
dev member may point to the wrong struct device instance, causing the
counter sub-driver to do runtime PM actions on the wrong device.&lt;/p&gt;
&lt;p&gt;To fix this, use the parent pointer of the counter, which is assigned
during probe to the correct struct device, not the struct device pointer
inside the shared struct rz_mtu3_channel.&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;counter: rz-mtu3-cnt: do not use struct rz_mtu3_channel&amp;#39;s dev member&lt;/p&gt;
&lt;p&gt;The counter driver can use HW channels 1 and 2, while the PWM driver can
use HW channels 0, 1, 2, 3, 4, 6, 7.&lt;/p&gt;
&lt;p&gt;The dev member is assigned both by the counter driver and the PWM driver
for channels 1 and 2, to their own struct device instance, overwriting
the previous value.&lt;/p&gt;
&lt;p&gt;The sub-drivers race to assign their own struct device pointer to the
same struct rz_mtu3_channel&amp;#39;s dev member.&lt;/p&gt;
&lt;p&gt;The dev member of struct rz_mtu3_channel is used by the counter
sub-driver for runtime PM.&lt;/p&gt;
&lt;p&gt;Depending on the probe order of the counter and PWM sub-drivers, the
dev member may point to the wrong struct device instance, causing the
counter sub-driver to do runtime PM actions on the wrong device.&lt;/p&gt;
&lt;p&gt;To fix this, use the parent pointer of the counter, which is assigned
during probe to the correct struct device, not the struct device pointer
inside the shared struct rz_mtu3_channel.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31740</guid>
    </item>
  </channel>
</rss>
