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-89622HID: mcp2221: clear rxbuf after I2C/SMBus transfer completes

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 49 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

CVSS scores of CVE-2026-89622, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 94% of all CVEs (12 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 198bf4a226229e36dfe254493a45c71c3ffc7e57
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < bd146a8ff107c6d77e75597decbcd1df0d7900d6
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < d6c6b293173c0ea87189501cbd77e8fa677814a1
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 03c34309eb1bce1b3b5f7c4a94b703f419120383
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < 968546b676d992dd1da3e057d40598231f725996
    • affected 67a95c21463d066060b0f66d65a75d45bb386ffb – < db2333f88729c8aae062cb171ed058725ff5c901
  • Linux · Linux

    • affected 5.7
    • unaffected < 5.7
    • unaffected 6.1.191 – ≤ 6.1.*
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.111 – ≤ 6.12.*
    • unaffected 6.18.51 – ≤ 6.18.*
    • unaffected 7.2.4 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References6

Sources

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

Badge for a README or a ticket

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

Record last updated .