CVE-2026-93128: platform/x86: lg-laptop: Fix LED resource handling
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Fixed version: Linux Linux 3e91964aa74ab261aa15d9d96318eded2fd9d22a, 4f9f1448dac4927ce5160f3a4a295e08fb969d32, 4fbfe3714f645b6c64c9ba8faa83b27e4c9f2edd.
Low priority for now. Upgrade to Linux Linux 3e91964aa74ab261aa15d9d96318eded2fd9d22a, 4f9f1448dac4927ce5160f3a4a295e08fb969d32, 4fbfe3714f645b6c64c9ba8faa83b27e4c9f2edd or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 17, 2026
- Updated
- Oct 30, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 5.15affected
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before 4f9f1448dac4927ce5160f3a4a295e08fb969d32affected · git
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before fc45f6e4b86c2fa1cf742c23a373d777d066aa25affected · git
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before 4fbfe3714f645b6c64c9ba8faa83b27e4c9f2eddaffected · git
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before 9a85e2d35e54248aca39bad4f4152ed34de1995faffected · git
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before acc190322250562d5f28860f4ae1ebaf3e304fc2affected · git
- ae26278829a80ad0e60ff004de71e9276cee5dc0 and later · before 3e91964aa74ab261aa15d9d96318eded2fd9d22aaffected · git
- before 5.15not affected · semver
- 6.1.191 and later · up to and including 6.1.*not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | from 0 | — |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-93126Sep 17, 2026 · remoteproc: qcom_q6v5_adsp: Fix reference leak for device node0Monitor
- ← EarlierCVE-2026-93127Sep 17, 2026 · bpf: Drop scalar id on sign-extending narrowing stack fills31Monitor
- Later →CVE-2026-93129Sep 17, 2026 · platform/x86: dell-wmi-base: Fix handling of ultra performance key0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 3e91964aa74ab261aa15d9d96318eded2fd9d22a | Vendor (CNA) |
| Linux Linux | 4f9f1448dac4927ce5160f3a4a295e08fb969d32 | Vendor (CNA) |
| Linux Linux | 4fbfe3714f645b6c64c9ba8faa83b27e4c9f2edd | Vendor (CNA) |
| Linux Linux | 9a85e2d35e54248aca39bad4f4152ed34de1995f | Vendor (CNA) |
| Linux Linux | acc190322250562d5f28860f4ae1ebaf3e304fc2 | Vendor (CNA) |
| Linux Linux | fc45f6e4b86c2fa1cf742c23a373d777d066aa25 | Vendor (CNA) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/4f9f1448dac4927ce5160f3a4a295e08fb969d32
- git.kernel.org/stable/c/4fbfe3714f645b6c64c9ba8faa83b27e4c9f2edd
- git.kernel.org/stable/c/9a85e2d35e54248aca39bad4f4152ed34de1995f
- git.kernel.org/stable/c/acc190322250562d5f28860f4ae1ebaf3e304fc2
- git.kernel.org/stable/c/fc45f6e4b86c2fa1cf742c23a373d777d066aa25
Vendor advisories and official records. Exploit/PoC links are deliberately left out.