<?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 09:08:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31741 — counter: rz-mtu3-cnt: prevent counter from being toggled multiple times</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31741</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: prevent counter from being toggled multiple times&lt;/p&gt;
&lt;p&gt;Runtime PM counter is incremented / decremented each time the sysfs
enable file is written to.&lt;/p&gt;
&lt;p&gt;If user writes 0 to the sysfs enable file multiple times, runtime PM
usage count underflows, generating the following message.&lt;/p&gt;
&lt;p&gt;rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!&lt;/p&gt;
&lt;p&gt;At the same time, hardware registers end up being accessed with clocks
off in rz_mtu3_terminate_counter() to disable an already disabled
channel.&lt;/p&gt;
&lt;p&gt;If user writes 1 to the sysfs enable file multiple times, runtime PM
usage count will be incremented each time, requiring the same number of
0 writes to get it back to 0.&lt;/p&gt;
&lt;p&gt;If user writes 0 to the sysfs enable file while PWM is in progress, PWM
is stopped without counter being the owner of the underlying MTU3
channel.&lt;/p&gt;
&lt;p&gt;Check against the cached count_is_enabled value and exit if the user
is trying to set the same enable value.&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: prevent counter from being toggled multiple times&lt;/p&gt;
&lt;p&gt;Runtime PM counter is incremented / decremented each time the sysfs
enable file is written to.&lt;/p&gt;
&lt;p&gt;If user writes 0 to the sysfs enable file multiple times, runtime PM
usage count underflows, generating the following message.&lt;/p&gt;
&lt;p&gt;rz-mtu3-counter rz-mtu3-counter.0: Runtime PM usage count underflow!&lt;/p&gt;
&lt;p&gt;At the same time, hardware registers end up being accessed with clocks
off in rz_mtu3_terminate_counter() to disable an already disabled
channel.&lt;/p&gt;
&lt;p&gt;If user writes 1 to the sysfs enable file multiple times, runtime PM
usage count will be incremented each time, requiring the same number of
0 writes to get it back to 0.&lt;/p&gt;
&lt;p&gt;If user writes 0 to the sysfs enable file while PWM is in progress, PWM
is stopped without counter being the owner of the underlying MTU3
channel.&lt;/p&gt;
&lt;p&gt;Check against the cached count_is_enabled value and exit if the user
is trying to set the same enable value.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31741</guid>
    </item>
  </channel>
</rss>
