<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T23:47:26.316457+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-89622</id>
    <title>CVE-2026-89622 — HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes</title>
    <updated>2026-09-29T23:47:26.445704+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes</p>
<p>mcp_i2c_smbus_read() stores the caller-supplied buffer pointer in
mcp-&gt;rxbuf for the duration of a transfer but never clears it when the
transfer finishes or times out. Once the caller frees or reuses the
buffer, mcp-&gt;rxbuf becomes a dangling pointer. A delayed or spurious
MCP2221_I2C_GET_DATA report can then drive mcp2221_raw_event() to
memcpy device data into the freed memory, causing a write
use-after-free.</p>
<p>Route all return paths through a single exit point that clears
mcp-&gt;rxbuf and mcp-&gt;rxbuf_size, so that the existing !mcp-&gt;rxbuf guard
in the raw_event handler can reject any report arriving after the
transfer has ended.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-89622"/>
  </entry>
</feed>
