<?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:11:06 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64333 — USB: serial: digi_acceleport: fix write buffer corruption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64333</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;USB: serial: digi_acceleport: fix write buffer corruption&lt;/p&gt;
&lt;p&gt;The digi_write_inb_command() is supposed to wait for the write urb to
become available or return an error, but instead it updates the transfer
buffer and tries to resubmit the urb on timeout.&lt;/p&gt;
&lt;p&gt;To make things worse, for commands like break control where no timeout
is used, the driver would corrupt the urb immediately due to a broken
jiffies comparison (on 32-bit machines this takes five minutes of uptime
to trigger due to INITIAL_JIFFIES).&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing return on timeout and waiting
indefinitely when no timeout has been specified as intended.&lt;/p&gt;
&lt;p&gt;This issue was (sort of) flagged by Sashiko when reviewing an unrelated
change to the driver.&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;USB: serial: digi_acceleport: fix write buffer corruption&lt;/p&gt;
&lt;p&gt;The digi_write_inb_command() is supposed to wait for the write urb to
become available or return an error, but instead it updates the transfer
buffer and tries to resubmit the urb on timeout.&lt;/p&gt;
&lt;p&gt;To make things worse, for commands like break control where no timeout
is used, the driver would corrupt the urb immediately due to a broken
jiffies comparison (on 32-bit machines this takes five minutes of uptime
to trigger due to INITIAL_JIFFIES).&lt;/p&gt;
&lt;p&gt;Fix this by adding the missing return on timeout and waiting
indefinitely when no timeout has been specified as intended.&lt;/p&gt;
&lt;p&gt;This issue was (sort of) flagged by Sashiko when reviewing an unrelated
change to the driver.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64333</guid>
    </item>
  </channel>
</rss>
