CVE-2026-53120
Received Received - Intake
PCI Driver Override Race Condition in Linux Kernel

Publication date: 2026-06-24

Last updated on: 2026-06-24

Assigner: kernel.org

Description
In the Linux kernel, the following vulnerability has been resolved: PCI: 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-06-24
Generated
2026-06-25
AI Q&A
2026-06-24
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Impact Analysis

This vulnerability can lead to a use-after-free condition in the Linux kernel's PCI driver handling. Such a condition may cause system instability, crashes, or potentially allow an attacker to execute arbitrary code or escalate privileges by exploiting the unsafe access to kernel memory.

Executive Summary

This vulnerability exists in the Linux kernel's PCI subsystem where the driver_override field is accessed without proper locking. Specifically, when a driver is probed through the __driver_attach() function, the bus' match() callback is called without holding the device lock. This can lead to a use-after-free (UAF) condition because the driver_override field is accessed without synchronization.

The issue is fixed by using the driver-core driver_override infrastructure, which ensures proper locking internally to prevent this unsafe access.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-53120. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart