CVE-2026-31487

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

CVSS 3.1

5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

EPSS

0.1% chance of exploitation in the next 30 days; higher than 1% of CVEs (scores of 2026-10-25)

CWE

CWE-667

Published

2026-04-22

Modified

2026-10-21

Record from

the NVD, synced 2026-10-22

Affected

• linux:linux_kernel

References

• https://git.kernel.org/stable/c/6e8eb467bed6aa1a563dba8f366c9fd76ba0004e
• https://git.kernel.org/stable/c/c73a58661a760373d08a6883af4f0bb5cc991a67
• https://git.kernel.org/stable/c/cc34d77dd48708d810c12bfd6f5bf03304f6c824
• https://git.kernel.org/stable/c/e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0
• https://git.kernel.org/stable/c/eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0

Check your stackJSON