CVE-2026-31487

NameCVE-2026-31487
DescriptionIn 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".
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)
ReferencesDSA-6238-1

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
linux (PTS)bullseye5.10.223-1vulnerable
bullseye (security)5.10.251-4vulnerable
bookworm6.1.159-1vulnerable
bookworm (security)6.1.170-3vulnerable
trixie6.12.73-1vulnerable
trixie (security)6.12.86-1fixed
forky, sid7.0.4-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
linuxsourcetrixie6.12.85-1DSA-6238-1
linuxsource(unstable)6.19.11-1

Notes

https://git.kernel.org/linus/cc34d77dd48708d810c12bfd6f5bf03304f6c824 (7.0-rc6)

Search for package or bug name: Reporting problems