{
  "affected": [
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:13",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "urgency": "not yet assigned"
      },
      "package": {
        "ecosystem": "Debian:14",
        "name": "linux"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "details": "In the Linux kernel, the following vulnerability has been resolved:  HID: universal-pidff: stop the device when force-feedback init fails  universal_pidff_probe() starts the device with hid_hw_start() and then, if force-feedback initialisation fails, returns the error through a label that only does \"return error\".  The device is left started.  The HID core does not unwind on the driver's behalf.  __hid_device_probe() releases the devres group, closes the report and clears hdev-\u003edriver:  \tif (ret) { \t\tdevres_release_group(\u0026hdev-\u003edev, hdev-\u003edevres_group_id); \t\thid_close_report(hdev); \t\thdev-\u003edriver = NULL; \t}  The hidraw character device that hid_hw_start() registered through hid_connect() is allocated with kzalloc() and added with cdev_device_add(), so it is not devres-managed and survives that.  With hdev-\u003edriver NULL, hid_device_remove() skips hid_hw_stop() as well, because it only unwinds while a driver is still attached.  The registration therefore outlives the device on both paths.  Opening the surviving /dev/hidrawX writes into freed memory.  KASAN reports a use-after-free write from hidraw_open() -\u003e hid_hw_open() -\u003e the transport's open callback, which takes a spinlock inside the freed object. A descriptor that carries a PID usage page and no input reports is enough: hidraw claims the device so hid_hw_start() succeeds, while hid-\u003einputs stays empty so force-feedback init fails.  The other failure returns in hid_pidff_init_with_quirks() - no output reports, an allocation failure, pidff_init_fields(), pidff_check_autocenter(), an unusable effect count, input_ff_create() - all reach the same label.  Stop the device on that path.  hid-dr.c and hid-emsff.c, which start the device with the same HID_CONNECT_DEFAULT \u0026 ~HID_CONNECT_FF mask, already do this.  The two earlier gotos must keep returning without hid_hw_stop(), since neither has a started device, so give the path that fails after the start its own label.  Discovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e",
  "id": "DEBIAN-CVE-2026-89624",
  "modified": "2026-09-14T08:47:32.842176562Z",
  "published": "2026-09-11T20:19:47.750Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://security-tracker.debian.org/tracker/CVE-2026-89624"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "upstream": [
    "CVE-2026-89624"
  ]
}