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-93189HID: core: quiesce input in hid_hw_stop() to prevent use-after-free

Description

In the Linux kernel, the following vulnerability has been resolved: HID: core: quiesce input in hid_hw_stop() to prevent use-after-free A driver's probe calls hid_device_io_start() to enable input delivery, then fails at a later initialization step and unwinds via hid_hw_stop(). The unwind frees struct hidraw via hidraw_disconnect() while in-flight HID reports may still be running on another CPU, dereferencing the freed object through hidraw_report_event(). syzbot reports the resulting use-after-free for the corsair-psu HID driver. Edward Adam Davis posted a per-driver fix for corsair-psu that adds an explicit hid_device_io_stop() before hid_hw_stop() in the probe error path ("hwmon: prevent packets from going to driver for probe", 2026-04-28). Auditing the tree shows 15 drivers call hid_device_io_start(); 7 also call hid_device_io_stop() and 8 do not: drivers calling hid_device_io_start() without a matching hid_device_io_stop() before hid_hw_stop(): drivers/hwmon/corsair-psu.c (fix posted by Edward) drivers/hwmon/corsair-cpro.c drivers/hwmon/nzxt-kraken3.c drivers/hwmon/nzxt-smart2.c drivers/hwmon/gigabyte_waterforce.c drivers/hid/hid-logitech-dj.c drivers/hid/hid-nintendo.c drivers/hid/hid-mcp2221.c Roughly half of all callers of the API are exposed. Centralize the quiesce in hid_hw_stop() so callers do not have to remember the matching stop: if a driver has left hdev->io_started true on entry, call hid_device_io_stop() before hid_disconnect(). For the 7 drivers that already call hid_device_io_stop() correctly, hdev->io_started is false on entry, the guard short-circuits, and behavior is unchanged. No Fixes: tag because the affected drivers gained their hid_device_io_start() calls independently over years; the bug is a class-wide API misuse rather than a regression from one commit.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 32 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-93189, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Received3.1High8.8CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.32% · top 75% of all CVEs (16 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0744cb9520aade37e78f69134f3111086158f1d2
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < c876c437d188911685d8bed645416f2e86bd0354
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 6787f1828f5616f17250e108c0031fb96fd2cfe6
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 92cca302a4eaf65d1b38b3fb600b4ee5eb856a51
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 02246d8b462fd9bd90bc7ae7d6cab1acf69bcb87
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 544ebb25bd58f67e821573412ab7a982b9e02211
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < 0fecd89f979a8653b9a5b0816570329b7a94a081
    • affected 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – < a4bc41504690b7d7064931909874f5b98cd148b6
    • affected < 5.10.270
    • affected < 5.15.221
    • affected < 6.1.188
    • affected < 6.6.157
    • affected < 6.12.110
    • affected < 6.18.52
    • affected < 7.2.6
  • Linux · Linux

    • 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.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 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-93189 badge
[![CVE-2026-93189](https://cveledger.app/badge/CVE-2026-93189.svg)](https://cveledger.app/cve/CVE-2026-93189)

Record last updated .