CVE-2026-99326

Description

A flaw was found in the Linux kernel's Lenovo Legion Go S HID (Human Interface Device) driver. A local or physically present user could trigger a Denial of Service (DoS) by disconnecting the device during initialization. Because the device removal routine and an active background setup task attempt to acquire the same lock simultaneously, the conflicting operations lead to a deadlock that causes the system to hang.

Statement

This vulnerability is rated as Moderate because exploitation requires physical access to attach and rapidly disconnect a specific hardware device, or the ability to emulate such hardware within a virtualized guest. Exposure is restricted to deployments actively interacting with Lenovo Legion Go S controllers. A successful trigger results in a kernel deadlock leading to denial of service, but does not allow privilege escalation or compromise system confidentiality or integrity.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.2N/AN/A
Attack VectorPhysicalN/AN/A
Attack ComplexityHighN/AN/A
Privileges RequiredNoneN/AN/A
User InteractionNoneN/AN/A
ScopeUnchangedN/AN/A
ConfidentialityNoneN/AN/A
Integrity ImpactNoneN/AN/A
Availability ImpactHighN/AN/A

Vector

Red Hat: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Understanding the Weakness (CWE)

Availability

Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Other); DoS: Crash, Exit, or Restart

Each thread of execution will "hang" and prevent tasks from completing. In some cases, CPU consumption may occur if a lock check occurs in a tight loop.

Frequently Asked Questions

Want to get errata notifications? Sign up here.