GHSA-H5C7-P475-C26R
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind
For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghl_magic_poke() (the timer callback) submits sc->ghl_urb, and the URB completion ghl_magic_poke_cb() re-arms the timer with mod_timer().
sony_remove() drained the timer with timer_delete_sync() and then freed the URB with usb_free_urb():
timer_delete_sync(&sc->ghl_poke_timer);
usb_free_urb(sc->ghl_urb);
timer_delete_sync() does not block re-arming, and while the URB is in flight the timer is not pending, so the sync delete is a no-op. A URB completion that runs after the delete re-arms the timer, and usb_free_urb() only drops a reference -- it does not kill an in-flight URB. sc is allocated with devm_kzalloc() and freed once sony_remove() returns, so the re-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a use-after-free from timer softirq. This is a disconnect/rmmod race.
Poison the URB first, then shut the timer down, before freeing the URB. usb_poison_urb() kills any in-flight URB and permanently rejects further submissions, so a poke timer that is still pending cannot re-submit the URB from ghl_magic_poke() in the window before timer_shutdown_sync() runs. usb_kill_urb() would not suffice: it only cancels the in-flight URB and leaves it submittable once it returns, so the pending timer could re-submit it and put a fresh URB in flight over the freed sc. timer_shutdown_sync() then drains any last callback and blocks re-arming. The probe error path is unaffected: it is only reached before the timer is armed.
Reproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget emulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds and arms the poke timer, the poke URB is held in flight, the driver is unbound (freeing sc), then the URB is released. The completion re-arms the timer on the freed sc, and the re-armed timer fires ~8 s later:
BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0 Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0 ghl_magic_poke+0x98/0xb0 call_timer_fn+0x35/0x2b0 __run_timers+0x69c/0x9a0 run_timer_softirq+0x173/0x2a0 Allocated by task 169: sony_probe Freed by task 338: devres_release_group <- hid_device_remove (sony_remove)
Found by 0sec (https://0sec.ai) using automated source analysis.
{
"affected": [],
"aliases": [
"CVE-2026-89625"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:47Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nHID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind\n\nFor GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer:\nghl_magic_poke() (the timer callback) submits sc-\u003eghl_urb, and the URB\ncompletion ghl_magic_poke_cb() re-arms the timer with mod_timer().\n\nsony_remove() drained the timer with timer_delete_sync() and then freed\nthe URB with usb_free_urb():\n\n\ttimer_delete_sync(\u0026sc-\u003eghl_poke_timer);\n\tusb_free_urb(sc-\u003eghl_urb);\n\ntimer_delete_sync() does not block re-arming, and while the URB is in\nflight the timer is not pending, so the sync delete is a no-op. A URB\ncompletion that runs after the delete re-arms the timer, and usb_free_urb()\nonly drops a reference -- it does not kill an in-flight URB. sc is\nallocated with devm_kzalloc() and freed once sony_remove() returns, so the\nre-armed ghl_poke_timer (embedded in sc) then fires on freed memory, a\nuse-after-free from timer softirq. This is a disconnect/rmmod race.\n\nPoison the URB first, then shut the timer down, before freeing the URB.\nusb_poison_urb() kills any in-flight URB and permanently rejects further\nsubmissions, so a poke timer that is still pending cannot re-submit the\nURB from ghl_magic_poke() in the window before timer_shutdown_sync() runs.\nusb_kill_urb() would not suffice: it only cancels the in-flight URB and\nleaves it submittable once it returns, so the pending timer could\nre-submit it and put a fresh URB in flight over the freed sc.\ntimer_shutdown_sync() then drains any last callback and blocks re-arming.\nThe probe error path is unaffected: it is only reached before the timer\nis armed.\n\nReproduced under KASAN on next-20260710 via dummy_hcd + raw-gadget\nemulation of the GHL PS4 dongle (VID 0x1430 / PID 0x07bb): hid-sony binds\nand arms the poke timer, the poke URB is held in flight, the driver is\nunbound (freeing sc), then the URB is released. The completion re-arms the\ntimer on the freed sc, and the re-armed timer fires ~8 s later:\n\n BUG: KASAN: slab-use-after-free in ghl_magic_poke+0x98/0xb0\n Read of size 8 at addr ffff88810b02fd50 by task swapper/0/0\n ghl_magic_poke+0x98/0xb0\n call_timer_fn+0x35/0x2b0\n __run_timers+0x69c/0x9a0\n run_timer_softirq+0x173/0x2a0\n Allocated by task 169: sony_probe\n Freed by task 338: devres_release_group \u003c- hid_device_remove (sony_remove)\n\nFound by 0sec (https://0sec.ai) using automated source analysis.",
"id": "GHSA-h5c7-p475-c26r",
"modified": "2026-09-11T21:31:34Z",
"published": "2026-09-11T21:31:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89625"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/114a58640aaf3c2eb97b5b01c75ab5e541d15d9c"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/3155dc327344d286f17345cd371be05e255a4328"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/a26705bd2e2728833e7a538ce91e58a5eeff496a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.