CVE-2026-89621

HID: mcp2221: validate report size in mcp2221_raw_event()

N/A
Published: September 11, 2026 at 07:45 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: HID: mcp2221: validate report size in mcp2221_raw_event() mcp2221_raw_event() never validates the size of incoming HID reports. In the MCP2221_I2C_GET_DATA path it trusts the device-supplied data[3] as the copy length without checking that 4 + data[3] bytes actually exist in the received report. A malicious or misbehaving USB device can send a short report with a large data[3], causing the memcpy to read past the valid report data in the HID transfer buffer and leak uninitialized kernel memory back to userspace through the I2C/SMBus read path. Add a minimum size check at entry and validate that the source range fits within the received report before the copy.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.767a95c21463d066060b0f66d65a75d45bb386ffb
Vendor states this is fixed in 127de5919820f88a9d55e8371ad4ac49f625f4c5 (fixed)
Vendor states this is fixed in 2c9a6998c19503626c57a2267bf279e204113079 (fixed)
Vendor states this is fixed in 7c18fb36708a97ff6772825cc087b6d537bbf0d5 (fixed)
Vendor states this is fixed in b2c67dc0e30c308647bbd9b9e5d69a44c9d2733d (fixed)
Vendor states this is fixed in bdc6a3af0dd734a326acdb7d6401a3b6a9f4f149 (fixed)
Vendor states this is fixed in c1c508e8923911cb458234997e55b7a4b9aa066f (fixed)
Vendor states this is fixed in cb38b1f149b7143355b37e86c841acf0076e5c2a (fixed)
Vendor states this is fixed in fffcfa367072628c3144cca17d2a3c3c9e50c057 (fixed)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 5.7 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.109 (unaffected)
Vendor states this is fixed in 6.18.50 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.4 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card