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

Published Jul 25, 2026
·
Updated

HID: lg-g15: cancel pending work on remove to fix a use-after-free

Affected Software

11 affected componentsFixes available
Linux Kernel
Microsoft azl3 kernel 6.6.144.1-1<6.6.145.2-1
6.6.145.2-1
Linux Linux kernel>=5.5<5.10.261
Linux Linux kernel>=5.11<5.15.212
Linux Linux kernel>=5.16<6.1.178
Linux Linux kernel>=6.2<6.6.145
Linux Linux kernel>=6.7<6.12.96
Linux Linux kernel>=6.13<6.18.39
Linux Linux kernel>=6.19<7.1.4
Linux Linux kernel=7.2-rc1
Linux Linux kernel=7.2-rc2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.145.2-1
  2. Remove

    Remove linux kernel driver: lg-g15 (HID: lg-g15) from your environment.

    Add a remove callback that cancels pending work before devres frees lg_g15_data to fix a use-after-free on device unplug.

  3. Configuration

    In the driver’s remove callback, cancel the scheduled work (e.g., via cancel on g15->work.func) to avoid cancelling a work item that was never set for models that do not initialize g15->work.

    lg-g15 (HID: lg-g15) driver remove callback: cancel pending work = cancel pending work on remove (with a NULL/guard test matching the g15 NULL test in lg_g15_raw_event())

Event History

Jul 25, 2026
CVE Published
via MITRE·08:50 AM
Data Sourced
via MITRE·08:50 AM
Description
Data Sourced
via NVD·10:17 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jul 26, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:06 AM
Affected Software
Updated
via Microsoft·08:06 AM
DescriptionSeverity

Frequently Asked Questions

1

Which devices and actions can trigger the vulnerable path?

The affected work item is used by the Logitech G15, G15 v2, and G510 HID driver paths. It can be scheduled by device input, including the backlight cycle key handling for G15 and G15 v2; the G510 LED event handler can also schedule it.

2

What must happen for exploitation to be possible?

An attacker needs local access and low privileges, and must win a race where the device schedules the work and is then unplugged while that work is pending or running. The worker can then dereference driver state after it has been freed.

3

Are all models handled by this driver affected?

No. The described uninitialized-work concern applies to G13 and Z-10, which do not set up the work item that is cancelled during removal. The use-after-free path described involves models that initialize and schedule that work: G15, G15 v2, and G510.

4

What is the remediation?

Apply a kernel update containing the remove callback that cancels pending work before device-managed driver state is freed. The referenced stable commits provide the fix.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203