Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-89621HID: mcp2221: validate report size in mcp2221_raw_event()

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 38 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.22% · top 87% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < cb38b1f149b7143355b37e86c841acf0076e5c2a
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < b2c67dc0e30c308647bbd9b9e5d69a44c9d2733d
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < fffcfa367072628c3144cca17d2a3c3c9e50c057
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < c1c508e8923911cb458234997e55b7a4b9aa066f
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < bdc6a3af0dd734a326acdb7d6401a3b6a9f4f149
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 127de5919820f88a9d55e8371ad4ac49f625f4c5
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 7c18fb36708a97ff6772825cc087b6d537bbf0d5
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 2c9a6998c19503626c57a2267bf279e204113079
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.109 – ≤ 6.12.*
    • unaffected 6.18.50 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-89621 badge
[![CVE-2026-89621](https://cveledger.app/badge/CVE-2026-89621.svg)](https://cveledger.app/cve/CVE-2026-89621)

Record last updated .