<?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 02:32:42 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-90124 — irqchip/renesas-rzg2l: Fix loss of interrupt</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-90124</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;irqchip/renesas-rzg2l: Fix loss of interrupt&lt;/p&gt;
&lt;p&gt;rzg2l_clear_irq_int() and rzg2l_clear_tint_int() perform a
read-modify-write on the ISCR/TSCR status registers to clear the bit
for the interrupt just handled. Since these registers are
write-0-to-clear per bit, this is racy:&lt;/p&gt;
&lt;p&gt;If another interrupt&amp;#39;s status bit gets set between the read and the write,
that bit is written back as 0 by the software-constructed value, clearing
an interrupt that hasn&amp;#39;t been serviced yet and losing it.&lt;/p&gt;
&lt;p&gt;This can be reproduced by triggering multiple interrupts at once, e.g.:&lt;/p&gt;
&lt;p&gt;gpioset -c gpiochip0 355=0 353=0 328=0 352=0&lt;/p&gt;
&lt;p&gt;Fix this by writing back only the bit being cleared, with all other bits
set to 1, instead of read-modify-writing the whole register.  Since 1-bits
are left unchanged by hardware, concurrently-set status bits for other
interrupts are preserved.&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;irqchip/renesas-rzg2l: Fix loss of interrupt&lt;/p&gt;
&lt;p&gt;rzg2l_clear_irq_int() and rzg2l_clear_tint_int() perform a
read-modify-write on the ISCR/TSCR status registers to clear the bit
for the interrupt just handled. Since these registers are
write-0-to-clear per bit, this is racy:&lt;/p&gt;
&lt;p&gt;If another interrupt&amp;#39;s status bit gets set between the read and the write,
that bit is written back as 0 by the software-constructed value, clearing
an interrupt that hasn&amp;#39;t been serviced yet and losing it.&lt;/p&gt;
&lt;p&gt;This can be reproduced by triggering multiple interrupts at once, e.g.:&lt;/p&gt;
&lt;p&gt;gpioset -c gpiochip0 355=0 353=0 328=0 352=0&lt;/p&gt;
&lt;p&gt;Fix this by writing back only the bit being cleared, with all other bits
set to 1, instead of read-modify-writing the whole register.  Since 1-bits
are left unchanged by hardware, concurrently-set status bits for other
interrupts are preserved.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-90124</guid>
    </item>
  </channel>
</rss>
