Unknown severity · Source severity not reportedCVE-2026-31487

spi: use generic driver_override infrastructureCVE-2026-31487

Answer in brief

CVE-2026-31487 records a Unknown severity vulnerability in spi: use generic driver_override infrastructure. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 22, 2026Updated Oct 21, 2026Source checked Oct 21, 2026First seen by HOL Oct 21, 2026Material review Oct 21, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=5039563e7c25eccd7fec1de6706011009d1c5665 <6e8eb467bed6aa1a563dba8f366c9fd76ba0004e \|\| >=5039563e7c25eccd7fec1de6706011009d1c5665 <eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0 \|\| >=5039563e7c25eccd7fec1de6706011009d1c5665 <c73a58661a760373d08a6883af4f0bb5cc991a67 \|\| >=5039563e7c25eccd7fec1de6706011009d1c5665 <e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0 \|\| >=5039563e7c25eccd7fec1de6706011009d1c5665 <cc34d77dd48708d810c12bfd6f5bf03304f6c824	6e8eb467bed6aa1a563dba8f366c9fd76ba0004e, eedf220442d13b6d97294e5b0ac8a2c38ee1a1a0, c73a58661a760373d08a6883af4f0bb5cc991a67, e0ae367a2de06c49aa1de6ec9b1ab6860bbb2cf0, cc34d77dd48708d810c12bfd6f5bf03304f6c824
Linux/Linuxgeneric	4.20	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to 6e8eb467bed6aa1a563dba8f366c9fd76ba0004e if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 21, 2026

Sources and claim methodology

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

Quoted source text, attributed separately from HOL analysis.