CVE-2026-89625HID: sony: fix UAF of ghl_poke_timer / ghl_urb at driver unbind
- —Not scoredno CVSS score yet
- 0.23%Exploitation in 30 daysEPSS · top 86% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In 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.
Timeline
ID reserved
By Linux
Published
- 49 days later
· 49 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
No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.
- EPSS (exploitation in 30 days)
- 0.23% · top 86% of all CVEs (15 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.
Affected products
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 9405e50a64b07d9c6216381d7eac5373e8ce5077
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 8c18db1d6618b37efdb819e35a44d16bfabf171b
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 56ef23198bdd51644372b1a9917802544b30987a
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 0e3d42ef008f0931e3878b4f1b046b6e45a95bde
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 114a58640aaf3c2eb97b5b01c75ab5e541d15d9c
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < 3155dc327344d286f17345cd371be05e255a4328
- affected cc894ac553605c9193a7a94372ff2f8af5766f46 – < a26705bd2e2728833e7a538ce91e58a5eeff496a
- affected 5.11
- unaffected < 5.11
- unaffected 5.15.224 – ≤ 5.15.*
- unaffected 6.1.191 – ≤ 6.1.*
- unaffected 6.6.160 – ≤ 6.6.*
- unaffected 6.12.111 – ≤ 6.12.*
- unaffected 6.18.50 – ≤ 6.18.*
- unaffected 7.2.4 – ≤ 7.2.*
- unaffected 7.3 – ≤ *
References
References7
- https://git.kernel.org/stable/c/9405e50a64b07d9c6216381d7eac5373e8ce5077 (opens in a new tab)
- https://git.kernel.org/stable/c/8c18db1d6618b37efdb819e35a44d16bfabf171b (opens in a new tab)
- https://git.kernel.org/stable/c/56ef23198bdd51644372b1a9917802544b30987a (opens in a new tab)
- https://git.kernel.org/stable/c/0e3d42ef008f0931e3878b4f1b046b6e45a95bde (opens in a new tab)
- https://git.kernel.org/stable/c/114a58640aaf3c2eb97b5b01c75ab5e541d15d9c (opens in a new tab)
- https://git.kernel.org/stable/c/3155dc327344d286f17345cd371be05e255a4328 (opens in a new tab)
- https://git.kernel.org/stable/c/a26705bd2e2728833e7a538ce91e58a5eeff496a (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-76537 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-89625)Record last updated .