<?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 15:10:58 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-64565 — Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-64565</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;Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()&lt;/p&gt;
&lt;p&gt;The `ims_pcu_process_data()` processes incoming URB data byte by byte.
However, it fails to check if the `read_pos` index exceeds
IMS_PCU_BUF_SIZE.&lt;/p&gt;
&lt;p&gt;If a malicious USB device sends a packet larger than IMS_PCU_BUF_SIZE,
`read_pos` will increment indefinitely. Moreover, since `read_pos` is
located immediately after `read_buf`, the attacker can overwrite
`read_pos` itself to arbitrarily control the index.&lt;/p&gt;
&lt;p&gt;This manipulated `read_pos` is subsequently used in
`ims_pcu_handle_response()` to copy data into `cmd_buf`, leading to a
heap buffer overflow.&lt;/p&gt;
&lt;p&gt;Specifically, an attacker can overwrite the `cmd_done.wait.head` located
at offset 136 relative to `cmd_buf` in the `ims_pcu_handle_response()`.
Consequently, when the driver calls `complete(&amp;amp;pcu-&amp;gt;cmd_done)`, it
triggers a control flow hijack by using the manipulated pointer.&lt;/p&gt;
&lt;p&gt;Fix this by adding a bounds check for `read_pos` before writing to
`read_buf`. If the packet is too long, discard it, log a warning,
and reset the parser state.&lt;/p&gt;
&lt;p&gt;[dtor: factor out resetting packet state, reset checksum as well]&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;Input: ims-pcu - fix heap-buffer-overflow in ims_pcu_process_data()&lt;/p&gt;
&lt;p&gt;The `ims_pcu_process_data()` processes incoming URB data byte by byte.
However, it fails to check if the `read_pos` index exceeds
IMS_PCU_BUF_SIZE.&lt;/p&gt;
&lt;p&gt;If a malicious USB device sends a packet larger than IMS_PCU_BUF_SIZE,
`read_pos` will increment indefinitely. Moreover, since `read_pos` is
located immediately after `read_buf`, the attacker can overwrite
`read_pos` itself to arbitrarily control the index.&lt;/p&gt;
&lt;p&gt;This manipulated `read_pos` is subsequently used in
`ims_pcu_handle_response()` to copy data into `cmd_buf`, leading to a
heap buffer overflow.&lt;/p&gt;
&lt;p&gt;Specifically, an attacker can overwrite the `cmd_done.wait.head` located
at offset 136 relative to `cmd_buf` in the `ims_pcu_handle_response()`.
Consequently, when the driver calls `complete(&amp;amp;pcu-&amp;gt;cmd_done)`, it
triggers a control flow hijack by using the manipulated pointer.&lt;/p&gt;
&lt;p&gt;Fix this by adding a bounds check for `read_pos` before writing to
`read_buf`. If the packet is too long, discard it, log a warning,
and reset the parser state.&lt;/p&gt;
&lt;p&gt;[dtor: factor out resetting packet state, reset checksum as well]&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-64565</guid>
    </item>
  </channel>
</rss>
