CVE-2026-53118

vdpa: 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:

vdpa: 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

A race condition in the Linux vdpa driver allows the bus match callback to read the driver_override field without holding the device lock. This unsynchronized access can trigger a use‑after‑free, corrupting kernel memory and potentially enabling an attacker to execute arbitrary code with kernel privileges. This vulnerability corresponds to a use‑after‑free condition (CWE‑416).

Affected Systems

All Linux kernel builds that contain the vdpa driver and have not applied the patch that redirects driver_override accesses to the driver‑core infrastructure. No specific kernel release numbers are provided; affected systems remain vulnerable until the patch from commit 654ef9c33e… is incorporated.

Risk and Exploitability

The CVSS score of 7.8 indicates high severity, and the EPSS score of less than 1% suggests a low but non‑zero exploitation probability. KEV has not listed this vulnerability, so there is no public catalog of known exploits. A kernel‑level use‑after‑free of this nature can permit local privilege escalation if an attacker can influence device probing or memory layout, so systems lacking the fix are considered at high risk until the kernel is updated.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Linux kernel version that includes the driver‑override fix introduced by commit 654ef9c33e…
  • Reboot the system to load the updated kernel
  • If an immediate kernel upgrade is not possible, disable the vdpa driver by removing it from the kernel configuration or unbinding any running virtual devices to prevent the problematic driver from being probed until the fix is available.

Generated by OpenCVE AI on August 12, 2026 at 07:18 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DLA Debian DLA DLA-4904-1 linux-6.12 security update
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-8781-1 Linux kernel (NVIDIA Tegra) 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
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Weaknesses CWE-413
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Type Values Removed Values Added
Weaknesses CWE-416
Type Values Removed Values Added
Description In the Linux kernel, the following vulnerability has been resolved: vdpa: 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 vdpa: 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
Nov 6, 2026, 4:24 PM
Reserved
Jun 9, 2026, 7:44 AM
Status
Modified
Published
Jun 24, 2026, 5:17 PM
Modified
Nov 6, 2026, 5:18 PM
Severity
Moderate
Public date
Jun 24, 2026, 12:00 AM