HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 67a95c21463d066060b0f66d65a75d45bb386ffb · < db2333f88729c8aae062cb171ed058725ff5c901| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes
mcp_i2c_smbus_read() stores the caller-supplied buffer pointer in mcp->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->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.
Route all return paths through a single exit point that clears mcp->rxbuf and mcp->rxbuf_size, so that the existing !mcp->rxbuf guard in the raw_event handler can reject any report arriving after the transfer has ended.
From the CVE record · Linux
The Linux kernel’s MCP2221 HID driver can retain a pointer to a caller’s buffer after an I2C/SMBus transfer ends or times out. If the buffer is freed or reused, a delayed or spurious MCP2221_I2C_GET_DATA report can cause a write use-after-free. The input does not specify network access, authentication requirements, or user interaction.
Engineers running Linux kernels with the MCP2221 HID driver should check their exposure; affected versions are not specified.