CVE-2026-89625

UNRATEDCVSS · not yet scoredTrending — 4 sources updated this week
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 11, 2026

Last Modified

September 21, 2026

References (4)

Vendor Advisories for CVE-2026-89625(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 13× in last 7d / 54× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 60 is merged into the row it repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-12 14:48 UTCEG score recompute
  4. 2026-10-11 19:15 UTCEG score recompute
  5. 2026-10-11 16:31 UTCEG score recompute
  6. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-11 13:47 UTCEG score recompute
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-10 12:53 UTCVendor advisory
  10. 2026-10-10 12:53 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-07 09:05 UTCVendor advisory
  15. 2026-10-07 09:05 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-04 05:22 UTCVendor advisory
  20. 2026-10-04 05:22 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  21. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-10-01 01:41 UTCEG score recompute
  23. 2026-10-01 01:41 UTCVendor advisory
  24. 2026-10-01 01:41 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  25. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
Show 34 more
  1. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  2. 2026-09-27 22:00 UTCVendor advisory
  3. 2026-09-27 22:00 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  4. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  5. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  6. 2026-09-24 18:14 UTCVendor advisory
  7. 2026-09-24 18:14 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  8. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  9. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  11. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  12. 2026-09-21 14:21 UTCVendor advisory
  13. 2026-09-21 14:21 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  14. 2026-09-21 14:20 UTCNVD update
  15. 2026-09-21 13:21 UTCVendor advisory
  16. 2026-09-21 13:21 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  17. 2026-09-21 13:20 UTCMITRE cvelistV5
  18. 2026-09-21 07:46 UTCVendor advisory
  19. 2026-09-21 07:46 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  20. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-09-18 04:05 UTCVendor advisory
  23. 2026-09-18 04:05 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  24. 2026-09-17 19:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-09-16 14:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  28. 2026-09-15 00:22 UTCEG score recompute
  29. 2026-09-15 00:22 UTCGHSA enrichmentGHSA-h5c7-p475-c26r
  30. 2026-09-13 16:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  31. 2026-09-12 15:02 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  32. 2026-09-11 20:36 UTCNVD update
  33. 2026-09-11 19:49 UTCEG score recompute
  34. 2026-09-11 19:49 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-89625?
CVE-2026-89625 is a vulnerability whose severity is not yet rated; its CVE record was published on September 11, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: sony: fix UAF of ghlpoketimer / ghl_urb at driver unbind For GHL (Guitar Hero Live) dongles, sony_probe() arms a periodic timer: ghlmagicpoke() (the timer callback) submits sc->ghl_urb, and the URB completion ghlmagicpokecb()…
When was the CVE record for CVE-2026-89625 published?
The CVE record for CVE-2026-89625 was published on September 11, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 21, 2026; the record at its source may have been updated since.
Is CVE-2026-89625 actively exploited?
CVE-2026-89625 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-89625?
A fix for CVE-2026-89625 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89625 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89625

Explore →

Is Your Infrastructure Affected by CVE-2026-89625?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs