<?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>Wed, 30 Sep 2026 01:09:22 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-44951 — serial: sc16is7xx: fix TX fifo corruption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-44951</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;serial: sc16is7xx: fix TX fifo corruption&lt;/p&gt;
&lt;p&gt;Sometimes, when a packet is received on channel A at almost the same time
as a packet is about to be transmitted on channel B, we observe with a
logic analyzer that the received packet on channel A is transmitted on
channel B. In other words, the Tx buffer data on channel B is corrupted
with data from channel A.&lt;/p&gt;
&lt;p&gt;The problem appeared since commit 4409df5866b7 (&amp;#34;serial: sc16is7xx: change
EFR lock to operate on each channels&amp;#34;), which changed the EFR locking to
operate on each channel instead of chip-wise.&lt;/p&gt;
&lt;p&gt;This commit has introduced a regression, because the EFR lock is used not
only to protect the EFR registers access, but also, in a very obscure and
undocumented way, to protect access to the data buffer, which is shared by
the Tx and Rx handlers, but also by each channel of the IC.&lt;/p&gt;
&lt;p&gt;Fix this regression first by switching to kfifo_out_linear_ptr() in
sc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer.&lt;/p&gt;
&lt;p&gt;Secondly, replace the chip-wise Rx buffer with a separate Rx buffer for
each 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;serial: sc16is7xx: fix TX fifo corruption&lt;/p&gt;
&lt;p&gt;Sometimes, when a packet is received on channel A at almost the same time
as a packet is about to be transmitted on channel B, we observe with a
logic analyzer that the received packet on channel A is transmitted on
channel B. In other words, the Tx buffer data on channel B is corrupted
with data from channel A.&lt;/p&gt;
&lt;p&gt;The problem appeared since commit 4409df5866b7 (&amp;#34;serial: sc16is7xx: change
EFR lock to operate on each channels&amp;#34;), which changed the EFR locking to
operate on each channel instead of chip-wise.&lt;/p&gt;
&lt;p&gt;This commit has introduced a regression, because the EFR lock is used not
only to protect the EFR registers access, but also, in a very obscure and
undocumented way, to protect access to the data buffer, which is shared by
the Tx and Rx handlers, but also by each channel of the IC.&lt;/p&gt;
&lt;p&gt;Fix this regression first by switching to kfifo_out_linear_ptr() in
sc16is7xx_handle_tx() to eliminate the need for a shared Rx/Tx buffer.&lt;/p&gt;
&lt;p&gt;Secondly, replace the chip-wise Rx buffer with a separate Rx buffer for
each channel.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-44951</guid>
    </item>
  </channel>
</rss>
