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".
References
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2026-04-22 14:16
Updated : 2026-06-17 10:33
NVD link : CVE-2026-31487
Mitre link : CVE-2026-31487
CVE.ORG link : CVE-2026-31487
JSON object : View
Products Affected
linux
- linux_kernel
CWE
CWE-667
Improper Locking
