All reports
Medium

kernel: spi: 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-31487

Probability of exploitation in the next 30 days: 0.12%

FIRST EPSS · 2026-11-21

Description

In the Linux kernel, the following vulnerability has been resolved: spi: 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] Also note that we do not enable the driver_override feature of struct bus_type, as SPI - in contrast to most other buses - passes "" to sysfs_emit() when the driver_override pointer is NULL. Thus, printing "\n" instead of "(null)\n".

A flaw was found in the Linux kernel, specifically within its Serial Peripheral Interface (SPI) subsystem. This vulnerability arises from improper handling of memory when a driver is being attached, leading to a use-after-free (UAF) condition. A UAF vulnerability is a type of memory corruption that can allow a local attacker to potentially escalate privileges or cause a system crash, impacting system stability and security.