CVE-2026-31487 json
spi: use generic driver_override infrastructure
published 2026-04-22 6 mo ago modified 2026-11-05 3 d ago also EUVD-2026-24853
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 1%
- public exploits
- 0
- none known
Summary
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".
Patch / fix
- Linux Linux 6.6.160, 6.12.80, 6.18.21, 6.19.11, 7.0
- linux Debian 13 6.12.85-1
- linux Debian 14 6.19.11-1
debian advisories DEBIAN-CVE-2026-31487
- linux Ubuntu 24.04 LTS 6.8.0-136.136
- linux-aws Ubuntu 24.04 LTS 6.8.0-1061.64
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1064.72
- linux-gke Ubuntu 24.04 LTS 6.8.0-1059.67
- linux-ibm Ubuntu 24.04 LTS 6.8.0-1061.62
- linux-azure Ubuntu 24.04 LTS 6.8.0-1063.71
- linux-gkeop Ubuntu 24.04 LTS 6.8.0-1046.50
- linux-raspi Ubuntu 24.04 LTS 6.8.0-1061.65
ubuntu advisories UBUNTU-CVE-2026-31487
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/6e8eb467bed6aa1a563dba8f366c9fd76ba0004e commit
- git.kernel.org/stable/c/eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0 commit
- git.kernel.org/stable/c/c73a58661a760373d08a6883af4f0bb5cc991a67 commit
- git.kernel.org/stable/c/e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0 commit
- git.kernel.org/stable/c/cc34d77dd48708d810c12bfd6f5bf03304f6c824 commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-31487 updated cvss 5.5
kernel: spi: use generic driver_override infrastructure
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernelaffected: no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 3 d ago
Exploit prediction
0.12% chance of exploitation in the next 30 days, higher than 1% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Weakness
-
- CWE-667 Improper Locking
- Technology feeds
References
- git.kernel.org /stable/c/6e8eb467bed6aa1a563dba8f366c9fd76ba0004e
-
git.kernel.org
/stable/c/eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0
patch
-
git.kernel.org
/stable/c/c73a58661a760373d08a6883af4f0bb5cc991a67
patch
-
git.kernel.org
/stable/c/e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0
patch
-
git.kernel.org
/stable/c/cc34d77dd48708d810c12bfd6f5bf03304f6c824
patch
Sources
- CVE List CVE-2026-31487
- NVD CVE-2026-31487
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.