CVE-2022-50131: HID: mcp2221: prevent a buffer overflow in mcp_smbus_write()
In the Linux kernel, the following vulnerability has been resolved:
HID: mcp2221: prevent a buffer overflow in mcp_smbus_write()
Smatch Warning:
drivers/hid/hid-mcp2221.c:388 mcp_smbus_write() error: __memcpy()
'&mcp->txbuf[5]' too small (59 vs 255)
drivers/hid/hid-mcp2221.c:388 mcp_smbus_write() error: __memcpy() 'buf'
too small (34 vs 255)
The 'len' variable can take a value between 0-255 as it can come from
data->block[0] and it is user data. So add an bound check to prevent a
buffer overflow in memcpy().
Security readout for executives and security teams
Plain-English summary
CVE-2022-50131 is a Linux kernel bug in the MCP2221 HID driver. A user-controlled length value could overflow a buffer during an SMBus write. Business urgency depends on whether affected kernels and this driver/device path are present. No active exploitation is reported in the provided sources.
Executive priority
Treat as a targeted kernel-maintenance issue, not an internet-wide emergency based on current evidence. Prioritize patch validation where Linux systems use MCP2221-related hardware or custom kernels. Keep it in regular kernel update cycles if the driver is absent or unreachable.
Technical view
The flaw is in drivers/hid/hid-mcp2221.c, mcp_smbus_write(). The CVE notes len can be 0-255 from data->block[0], while memcpy destinations/sources are smaller. Kernel stable commits add a bounds check to prevent overflow. CVSS, CWE, and complete impact details are not provided.
Likely exposure
Likely exposure is Linux systems running affected kernel versions with the MCP2221 HID driver reachable. This appears tied to a kernel hardware-driver path, not a general network service. Distribution backports may change exposure, so validate against vendor kernel advisories and package changelogs.
Exploitation context
The source bundle does not show CISA KEV listing, public exploitation, or exploit availability. The plausible risk is kernel memory corruption when the vulnerable driver processes oversized user-controlled block length data. Practical exploitability and privileges required are not specified in the provided sources.
Researcher notes
Evidence is limited to the CVE record and kernel stable commits. The affected-version data in the bundle is not fully normalized, so avoid relying only on raw version strings. Validate by commit presence, distribution advisory status, and whether the driver path is enabled.
Mitigation direction
Update to a vendor kernel containing the referenced stable fix.
Check Linux distribution advisories for backported patches and supported package versions.
If updates are delayed, consult vendor guidance for safe interim controls.
Prioritize systems where MCP2221 hardware or the hid-mcp2221 driver is used.
Validation and detection
Inventory Linux kernel versions across servers, workstations, and embedded systems.
Check whether hid-mcp2221 is built, loaded, or packaged in target kernels.
Confirm installed kernel includes one of the referenced stable commits or a distro backport.
Review vendor changelogs for CVE-2022-50131 or the MCP2221 bounds-check fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2022-50131 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
6Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Jun 18, 2025, 11:02 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.