<?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://db.gcve.eu</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>Sat, 24 Oct 2026 21:20:08 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99022 — regulator: ltc3676: don't read the write-only HRST and CLIRQ registers</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99022</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;regulator: ltc3676: don&amp;#39;t read the write-only HRST and CLIRQ registers&lt;/p&gt;
&lt;p&gt;HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST
triggers a hard reset of the chip and writing CLIRQ clears the interrupt;
reading them returns nothing useful, and the read itself fires the command.&lt;/p&gt;
&lt;p&gt;The result is that a plain register dump resets the board:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/regmap/2-003c/registers&lt;/p&gt;
&lt;p&gt;walks every readable register, hits HRST, and the board reboots.&lt;/p&gt;
&lt;p&gt;Split the callback back in two so HRST and CLIRQ stay writable but are no
longer readable. The readable range is left unchanged
(LTC3676_BUCK1 ... LTC3676_IRQSTAT).&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;regulator: ltc3676: don&amp;#39;t read the write-only HRST and CLIRQ registers&lt;/p&gt;
&lt;p&gt;HRST (0x1e) and CLIRQ (0x1f) are write-only command strobes. Writing HRST
triggers a hard reset of the chip and writing CLIRQ clears the interrupt;
reading them returns nothing useful, and the read itself fires the command.&lt;/p&gt;
&lt;p&gt;The result is that a plain register dump resets the board:&lt;/p&gt;
&lt;p&gt;cat /sys/kernel/debug/regmap/2-003c/registers&lt;/p&gt;
&lt;p&gt;walks every readable register, hits HRST, and the board reboots.&lt;/p&gt;
&lt;p&gt;Split the callback back in two so HRST and CLIRQ stay writable but are no
longer readable. The readable range is left unchanged
(LTC3676_BUCK1 ... LTC3676_IRQSTAT).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99022</guid>
    </item>
  </channel>
</rss>
