CVE-2026-31487: spi: use generic driver_override infrastructure

Severity: medium (CVSS 5.5 v3.1)
Exploited in the wild: not listed in CISA KEV
EPSS: 0.1% probability of exploitation in the next 30 days
Public exploit or detection template: none known
Published: 2026-04-22 · updated 2026-10-21
Weakness: CWE-667

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".

Affected products

Linux kernel: from 4.20.1 before 6.12.80; from 6.13 before 6.18.21; from 6.19 before 6.19.11; 4.20, 7.0-rc1, 7.0-rc2, 7.0-rc3, 7.0-rc4, 7.0-rc5 (+2) — fixed in 6.12.80, 6.18.21, 6.19.11

How to fix

Upgrade to a fixed version: Linux kernel 6.12.80, 6.18.21, 6.19.11. Check the vendor advisory for mitigations.

References

Get alerted when CVE-2026-31487 or the next vulnerability affects your stack