CVE-2026-64362

UnknownEPSS 0.18%

Last modified

CVE-2026-64362 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.18% chance of exploitation in the next 30 days.

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().

Metrics

EPSS Probability
0.18%

7.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 97b741aba918c4143f4208d2421d08ff215c1b49, < 3b9a3919aac6977262f04d5365c0456877522a44; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < 4aef9676c26dff8723b56834951cfc6b618f0986; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < acce9dee807f21184fff19ad17c8ed464247e7f7; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < 33cd1a000daf929356aacf2b191d31714ff0615e; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < dfc6e61f83113cc18346b6988f07271c0063357d; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < 4d0d51bc12d246accbfbb94de05d729c68c9b8fb; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < 8131f4226688c4be5f30874d167e44dab838eb09; >= 97b741aba918c4143f4208d2421d08ff215c1b49, < 7705b4140d188ce22656f6e541ae7ef834c7e11a
LinuxLinux5.5

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is CVE-2026-64362?
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().
How severe is CVE-2026-64362?
Severity scoring for CVE-2026-64362 is pending analysis. The EPSS model estimates a 0.18% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64362?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-64362?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST