CVE-2026-53119

platform/wmi: use generic driver_override infrastructure

Published Jun 24, 2026 CVSS 3.1 · 7.8 High EPSS < 1% KEV · Not listed
Description
In the Linux kernel, the following vulnerability has been resolved:

platform/wmi: use generic driver_override infrastructure

When a driver is probed through __driver_attach(), the bus' match()
callback is called without the device lock held, thus accessing the
driver_override field without a lock, which can cause a UAF.

Fix this by using the driver-core driver_override infrastructure taking
care of proper locking internally.

Note that calling match() from __driver_attach() without the device lock
held is intentional. [1]

Analysis

AI-generated

Technical impact

An unlocked race condition during device driver probing allows the bus match() callback to access the driver_override field without holding the device lock, resulting in a use‑after‑free. The resulting kernel memory corruption could crash the system or, if an attacker can control memory contents, lead to arbitrary code execution with kernel privileges.

Affected Systems

All Linux kernel releases that have not incorporated the commit replacing the direct driver_override access with the driver‑core infrastructure. The vulnerability affects every Linux distribution that ships the older kernel code, with no specific version range listed in the advisory.

Risk and Exploitability

The CVSS score of 7.8 and an EPSS of less than 1% indicate severe potential impact but a very low likelihood of exploitation. Because the flaw depends on a timing race during bus probing, it is most likely exploitable only from a local context that can trigger or influence device attachments. The vulnerability is not listed in CISA KEV. No remote exploitation path is documented.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply a kernel update that includes the driver‑core driver_override fix.
  • Recompile and reinstall any custom or third‑party kernel modules that perform device registration to ensure they reference the updated core logic.
  • As an interim measure, disable or restrict the WMI or other bus components that invoke __driver_attach until the kernel update can be applied.

Generated by OpenCVE AI on August 13, 2026 at 14:29 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Ubuntu USN Ubuntu USN USN-8566-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8568-1 Linux kernel (OEM) vulnerabilities
Ubuntu USN Ubuntu USN USN-8569-1 Linux kernel (HWE) vulnerabilities
Ubuntu USN Ubuntu USN USN-8593-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8603-1 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8618-1 Linux kernel vulnerabilities
Ubuntu USN Ubuntu USN USN-8663-1 Linux kernel (NVIDIA) vulnerabilities
Ubuntu USN Ubuntu USN USN-8664-1 Linux kernel (NVIDIA BaseOS) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-1 Linux kernel (GCP) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-2 Linux kernel (Azure) vulnerabilities
Ubuntu USN Ubuntu USN USN-8728-3 Linux kernel (Oracle) vulnerabilities
History
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: platform/wmi: use generic driver_override infrastructure When a driver is probed through __driver_attach(), the bus' match() callback is called without the device lock held, thus accessing the driver_override field without a lock, which can cause a UAF. Fix this by using the driver-core driver_override infrastructure taking care of proper locking internally. Note that calling match() from __driver_attach() without the device lock held is intentional. [1]
Title platform/wmi: use generic driver_override infrastructure
First Time appeared Linux
Linux linux Kernel
CPEs cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
Vendors & Products Linux
Linux linux Kernel
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Linux
Published
Updated
Jun 24, 2026, 4:30 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Analyzed
Published
Jun 24, 2026, 5:17 PM
Modified
Jul 23, 2026, 9:31 PM
Severity
Public date
Jun 24, 2026, 12:00 AM