<?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 01:38:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-40222 — tty: serial: sh-sci: fix RSCI FIFO overrun handling</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-40222</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;tty: serial: sh-sci: fix RSCI FIFO overrun handling&lt;/p&gt;
&lt;p&gt;The receive error handling code is shared between RSCI and all other
SCIF port types, but the RSCI overrun_reg is specified as a memory
offset, while for other SCIF types it is an enum value used to index
into the sci_port_params-&amp;gt;regs array, as mentioned above the
sci_serial_in() function.&lt;/p&gt;
&lt;p&gt;For RSCI, the overrun_reg is CSR (0x48), causing the sci_getreg() call
inside the sci_handle_fifo_overrun() function to index outside the
bounds of the regs array, which currently has a size of 20, as specified
by SCI_NR_REGS.&lt;/p&gt;
&lt;p&gt;Because of this, we end up accessing memory outside of RSCI&amp;#39;s
rsci_port_params structure, which, when interpreted as a plat_sci_reg,
happens to have a non-zero size, causing the following WARN when
sci_serial_in() is called, as the accidental size does not match the
supported register sizes.&lt;/p&gt;
&lt;p&gt;The existence of the overrun_reg needs to be checked because
SCIx_SH3_SCIF_REGTYPE has overrun_reg set to SCLSR, but SCLSR is not
present in the regs array.&lt;/p&gt;
&lt;p&gt;Avoid calling sci_getreg() for port types which don&amp;#39;t use standard
register handling.&lt;/p&gt;
&lt;p&gt;Use the ops-&amp;gt;read_reg() and ops-&amp;gt;write_reg() functions to properly read
and write registers for RSCI, and change the type of the status variable
to accommodate the 32-bit CSR register.&lt;/p&gt;
&lt;p&gt;sci_getreg() and sci_serial_in() are also called with overrun_reg in the
sci_mpxed_interrupt() interrupt handler, but that code pat…&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;tty: serial: sh-sci: fix RSCI FIFO overrun handling&lt;/p&gt;
&lt;p&gt;The receive error handling code is shared between RSCI and all other
SCIF port types, but the RSCI overrun_reg is specified as a memory
offset, while for other SCIF types it is an enum value used to index
into the sci_port_params-&amp;gt;regs array, as mentioned above the
sci_serial_in() function.&lt;/p&gt;
&lt;p&gt;For RSCI, the overrun_reg is CSR (0x48), causing the sci_getreg() call
inside the sci_handle_fifo_overrun() function to index outside the
bounds of the regs array, which currently has a size of 20, as specified
by SCI_NR_REGS.&lt;/p&gt;
&lt;p&gt;Because of this, we end up accessing memory outside of RSCI&amp;#39;s
rsci_port_params structure, which, when interpreted as a plat_sci_reg,
happens to have a non-zero size, causing the following WARN when
sci_serial_in() is called, as the accidental size does not match the
supported register sizes.&lt;/p&gt;
&lt;p&gt;The existence of the overrun_reg needs to be checked because
SCIx_SH3_SCIF_REGTYPE has overrun_reg set to SCLSR, but SCLSR is not
present in the regs array.&lt;/p&gt;
&lt;p&gt;Avoid calling sci_getreg() for port types which don&amp;#39;t use standard
register handling.&lt;/p&gt;
&lt;p&gt;Use the ops-&amp;gt;read_reg() and ops-&amp;gt;write_reg() functions to properly read
and write registers for RSCI, and change the type of the status variable
to accommodate the 32-bit CSR register.&lt;/p&gt;
&lt;p&gt;sci_getreg() and sci_serial_in() are also called with overrun_reg in the
sci_mpxed_interrupt() interrupt handler, but that code pat…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-40222</guid>
    </item>
  </channel>
</rss>
