CVE-2026-64362: Linux kernel · HID: lg-g15: cancel pending work on remove to fix a use-after-free
Affects Linux kernelSource GCVE Database
Not known to be exploited · CVSS 7.8 High · fixed in 5.15.0-1117.124~20.04.1 : patch Linux kernel soon.
Data as of 28 Oct 2026, 11:46 UTC
- Patch
- Available – fixed in 5.15.0-1117.124~20.04.1, 5.15.0-1123.132~20.04.1, 5.15.0-1122.131~20.04.1 +58
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 25 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Patches and advisories
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-4 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8876-1 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
In the Linux kernel, the following vulnerability has been resolved: HID: lg-g15: cancel pending work on remove to fix a use-after-free lg_g15_data is allocated with devm and holds a work item. The report handlers schedule that work straight from device input. lg_g15_event() and lg_g15_v2_event() do it on the backlight cycle key, and lg_g510_leds_event() does it too. The worker dereferences the lg_g15_data back through container_of. The driver had no remove callback and never cancelled the work. So if a report scheduled the work and the keyboard was then unplugged, devres freed lg_g15_data while the work was still pending or running, and the worker touched freed memory. This is a use-after-free. It is reachable as a race on device unplug. Add a remove callback that cancels the work before devres frees the state. g15->work is only initialized for the models that schedule it (G15, G15 v2, G510). The G13 and Z-10 leave it zeroed, so guard the cancel on g15->work.func to avoid cancelling a work that was never set up. The g15 NULL test mirrors the one already in lg_g15_raw_event().
References
- ubuntu.com/security/CVE-2026-64362 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-64362 (opens in a new tab)
- git.kernel.org/linus/7705b4140d188ce22656f6e541ae7ef834c7e11a (opens in a new tab)
- git.kernel.org/stable/c/33cd1a000daf929356aacf2b191d31714ff0615e (opens in a new tab)
- git.kernel.org/stable/c/3b9a3919aac6977262f04d5365c0456877522a44 (opens in a new tab)
- git.kernel.org/stable/c/4aef9676c26dff8723b56834951cfc6b618f0986 (opens in a new tab)
- git.kernel.org/stable/c/4d0d51bc12d246accbfbb94de05d729c68c9b8fb (opens in a new tab)
- git.kernel.org/stable/c/7705b4140d188ce22656f6e541ae7ef834c7e11a (opens in a new tab)
- git.kernel.org/stable/c/8131f4226688c4be5f30874d167e44dab838eb09 (opens in a new tab)
- git.kernel.org/stable/c/acce9dee807f21184fff19ad17c8ed464247e7f7 (opens in a new tab)
- git.kernel.org/stable/c/dfc6e61f83113cc18346b6988f07271c0063357d (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8727-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8726-3 (opens in a new tab)
- ubuntu.com/security/notices/USN-8800-1 (opens in a new tab)
- ubuntu.com/security/notices/USN-8760-2 (opens in a new tab)
- ubuntu.com/security/notices/USN-8728-2 (opens in a new tab)