# CVE-2026-93128: platform/x86: lg-laptop: Fix LED resource handling

> A null pointer dereference in the Linux kernel LG laptop driver can cause a system crash when handling LED resources.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 17 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-102917, BELL-CVE-2026-93128, DEBIAN-CVE-2026-93128, GHSA-9hr7-r765-xm77, UBUNTU-CVE-2026-93128

## What is CVE-2026-93128?

CVE-2026-93128 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

platform/x86: lg-laptop: Fix LED resource handling

The event notification callback might access kbd_backlight even
when it was not successfully registered with the LED subsystem.
The same happens inside acpi_remove(), where the LED devices are
unregistered unconditionally.

Fix this by tracking the availability of the kbd_backlight LED
device and use devm_led_classdev_register() to let devres take
care of unregistering the LED devices during removal. For this
the parent device of the LED devices is changed to the native
platform device.

## Which versions are affected by CVE-2026-93128?


## How do I fix CVE-2026-93128?

Apply the vendor's patch.

## Is CVE-2026-93128 being exploited?

There is no known exploitation of CVE-2026-93128 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93128 and fix it if it is affected.

What it is: CVE-2026-93128 is a vulnerability in Linux, published on 17 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93128 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93128/ (Markdown: https://insights.sbomify.com/CVE-2026-93128/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93128
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93128
- OSV: https://osv.dev/vulnerability/CVE-2026-93128

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93128/
Summaries are generated and may contain mistakes; the official description above is the record.