CVE-2026-93189

CVE CVE-2026-93189EUVD EUVD-2026-82297Veröffentlicht 2026-09-17T16:12:14.000ZZuletzt geändert 2026-09-18T17:56:26.000ZCVSS 8.8

Was das Advisory beschreibt

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.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux patch: 6.1.188; patch: 6.12.110; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <544ebb25bd58f67e821573412ab7a982b9e02211; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <c876c437d188911685d8bed645416f2e86bd0354; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0744cb9520aade37e78f69134f3111086158f1d2; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a4bc41504690b7d7064931909874f5b98cd148b6; 0 <6.1.188; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6787f1828f5616f17250e108c0031fb96fd2cfe6; 0 <7.2.6; 0 <6.18.52; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <92cca302a4eaf65d1b38b3fb600b4ee5eb856a51; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <02246d8b462fd9bd90bc7ae7d6cab1acf69bcb87; 0 <6.12.110; patch: 6.6.157; patch: 5.10.270; 0 <6.6.157; patch: 6.18.52; 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <0fecd89f979a8653b9a5b0816570329b7a94a081; patch: 7.2.6; 0 <5.10.270; patch: 5.15.221; 0 <5.15.221; patch: 7.3-rc1

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.