Skip to main content
VulnerabilityPublished Updated

CVE-2026-64362: Linux kernel · HID: lg-g15: cancel pending work on remove to fix a use-after-free

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in dfc6e61f83113cc18346b6988f07271c0063357d : update Linux kernel when convenient.

Data as of 6 Nov 2026, 17:04 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-06.

Patch
Available – fixed in dfc6e61f83113cc18346b6988f07271c0063357d, acce9dee807f21184fff19ad17c8ed464247e7f7, 8131f4226688c4be5f30874d167e44dab838eb09 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 6 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < dfc6e61f83113cc18346b6988f07271c0063357d
Fixed in
  • dfc6e61f83113cc18346b6988f07271c0063357d
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < acce9dee807f21184fff19ad17c8ed464247e7f7
Fixed in
  • acce9dee807f21184fff19ad17c8ed464247e7f7
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < 8131f4226688c4be5f30874d167e44dab838eb09
Fixed in
  • 8131f4226688c4be5f30874d167e44dab838eb09
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < 7705b4140d188ce22656f6e541ae7ef834c7e11a
Fixed in
  • 7705b4140d188ce22656f6e541ae7ef834c7e11a
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < 33cd1a000daf929356aacf2b191d31714ff0615e
Fixed in
  • 33cd1a000daf929356aacf2b191d31714ff0615e
LinuxLinuxAffected
  • ≥ 97b741aba918c4143f4208d2421d08ff215c1b49, < 4d0d51bc12d246accbfbb94de05d729c68c9b8fb
Fixed in
  • 4d0d51bc12d246accbfbb94de05d729c68c9b8fb

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

Community reviews

Loading reviews…