spi: use generic driver_override infrastructure
Summary
| CVE | CVE-2026-31487 |
| State | PUBLISHED |
| Assigner | Linux |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-04-22 14:16:46 UTC |
| Updated | 2026-04-22 14:16:46 UTC |
| 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". |
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|
| CNA |
Linux |
Linux |
affected 5039563e7c25eccd7fec1de6706011009d1c5665 eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5039563e7c25eccd7fec1de6706011009d1c5665 c73a58661a760373d08a6883af4f0bb5cc991a67 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5039563e7c25eccd7fec1de6706011009d1c5665 e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0 git |
Not specified |
| CNA |
Linux |
Linux |
affected 5039563e7c25eccd7fec1de6706011009d1c5665 cc34d77dd48708d810c12bfd6f5bf03304f6c824 git |
Not specified |
| CNA |
Linux |
Linux |
affected 4.20 |
Not specified |
| CNA |
Linux |
Linux |
unaffected 4.20 semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.12.80 6.12.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.18.21 6.18.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 6.19.11 6.19.* semver |
Not specified |
| CNA |
Linux |
Linux |
unaffected 7.0 * original_commit_for_fix |
Not specified |
References
| Reference | Source | Link | Tags |
|---|
| git.kernel.org/stable/c/e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/c73a58661a760373d08a6883af4f0bb5cc991a67 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| git.kernel.org/stable/c/cc34d77dd48708d810c12bfd6f5bf03304f6c824 |
416baaa9-dc9f-4396-8d5f-8c081fb06d67 |
git.kernel.org |
|
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.