{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-89624 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-89624 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-89624 and fix it if it is affected.\n\nWhat it is: CVE-2026-89624 is a high-severity use after free vulnerability in Linux, published on 11 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-89624 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-89624/ (Markdown: https://insights.sbomify.com/CVE-2026-89624/index.md)","id":"CVE-2026-89624","markdown":"https://insights.sbomify.com/CVE-2026-89624/index.md","name":"CVE-2026-89624","record":{"aliases":["AZL-100731","BELL-CVE-2026-89624","DEBIAN-CVE-2026-89624","GHSA-xwr6-736m-c3p5","UBUNTU-CVE-2026-89624"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel HID driver","requires_auth":"low_privilege","summary":"A use-after-free vulnerability in the Linux kernel's universal-pidff HID driver allows local attackers to execute code or escalate privileges via a malicious device.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nHID: universal-pidff: stop the device when force-feedback init fails\n\nuniversal_pidff_probe() starts the device with hid_hw_start() and then, if\nforce-feedback initialisation fails, returns the error through a label that\nonly does \"return error\".  The device is left started.\n\nThe HID core does not unwind on the driver's behalf.  __hid_device_probe()\nreleases the devres group, closes the report and clears hdev-\u003edriver:\n\n\tif (ret) {\n\t\tdevres_release_group(\u0026hdev-\u003edev, hdev-\u003edevres_group_id);\n\t\thid_close_report(hdev);\n\t\thdev-\u003edriver = NULL;\n\t}\n\nThe hidraw character device that hid_hw_start() registered through\nhid_connect() is allocated with kzalloc() and added with cdev_device_add(),\nso it is not devres-managed and survives that.  With hdev-\u003edriver NULL,\nhid_device_remove() skips hid_hw_stop() as well, because it only unwinds\nwhile a driver is still attached.  The registration therefore outlives the\ndevice on both paths.\n\nOpening the surviving /dev/hidrawX writes into freed memory.  KASAN reports\na use-after-free write from hidraw_open() -\u003e hid_hw_open() -\u003e the\ntransport's open callback, which takes a spinlock inside the freed object.\nA descriptor that carries a PID usage page and no input reports is enough:\nhidraw claims the device so hid_hw_start() succeeds, while hid-\u003einputs\nstays empty so force-feedback init fails.  The other failure returns in\nhid_pidff_init_with_quirks() - no output reports, an allocation failure,\npidff_init_fields(), pidff_check_autocenter(), an unusable effect count,\ninput_ff_create() - all reach the same label.\n\nStop the device on that path.  hid-dr.c and hid-emsff.c, which start the\ndevice with the same HID_CONNECT_DEFAULT \u0026 ~HID_CONNECT_FF mask, already do\nthis.  The two earlier gotos must keep returning without hid_hw_stop(),\nsince neither has a started device, so give the path that fails after the\nstart its own label.\n\nDiscovered by XBOW, triaged by Baul Lee \u003cbaul.lee@xbow.com\u003e","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"HID: universal-pidff: stop the device when force-feedback init fails","id":"CVE-2026-89624","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind","id":"CVE-2026-89625"},"packages":[],"prev":{"headline":"HID: mcp2221: stop device IO before hid_hw_stop","id":"CVE-2026-89623"},"products":["Linux"],"published":"2026-09-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["Linux"]},"summary":"A use-after-free vulnerability in the Linux kernel's universal-pidff HID driver allows local attackers to execute code or escalate privileges via a malicious device.","url":"https://insights.sbomify.com/CVE-2026-89624/"}