All reports
Medium

kernel: driver core: platform: use generic driver_override infrastructure

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-31527

Probability of exploitation in the next 30 days: 0.13%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: driver core: platform: 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]

A flaw was found in the Linux kernel. When a driver is probed, the match() callback can access the driver_override field without proper locking, leading to a Use-After-Free (UAF) vulnerability. This memory corruption flaw could allow a local attacker to escalate privileges or execute arbitrary code.