CVE-2026-53118

Awaiting Analysis Awaiting Analysis - Queue

VDPA Driver Override Use-After-Free in Linux Kernel

Publication date: 2026-06-24

Last updated on: 2026-07-14

Assigner: kernel.org

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]

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-06-24

Last Modified

2026-07-14

Generated

2026-07-15

AI Q&A

2026-06-24

EPSS Evaluated

2026-07-13

NVD

CVE-2026-53118

EUVD

EUVD-2026-38986

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability exists in the Linux kernel's vdpa driver. When a driver is probed using the __driver_attach() function, the bus' match() callback is invoked without holding the device lock. This leads to accessing the driver_override field without proper locking, which can cause a Use-After-Free (UAF) condition.

The issue is fixed by using the driver-core driver_override infrastructure that manages locking internally to prevent this unsafe access.

Impact Analysis

The vulnerability can lead to a Use-After-Free (UAF) condition in the Linux kernel. UAF vulnerabilities may allow attackers to execute arbitrary code, cause system crashes, or escalate privileges by exploiting the improper locking and memory access.

Hi! I’m here to help you understand CVE-2026-53118. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70