Answer in brief
CVE-2026-31527 records a Unknown severity vulnerability in driver core: platform: 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.
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.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=3d713e0e382e6fcfb4bba1501645b66c129ad60b <492349e5e4a369a8b62781100a3ade470bf1ce6b || >=3d713e0e382e6fcfb4bba1501645b66c129ad60b <9a6086d2a828dd2ff74cf9abcae456670febd71f || >=3d713e0e382e6fcfb4bba1501645b66c129ad60b <7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1 || >=3d713e0e382e6fcfb4bba1501645b66c129ad60b <edee7ee5a14c3b33f6d54641f5af5c5e9180992d || >=3d713e0e382e6fcfb4bba1501645b66c129ad60b <2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d | 492349e5e4a369a8b62781100a3ade470bf1ce6b, 9a6086d2a828dd2ff74cf9abcae456670febd71f, 7c02a9bd7d14a89065fcf672b86d8e1d1a41d3b1, edee7ee5a14c3b33f6d54641f5af5c5e9180992d, 2b38efc05bf7a8568ec74bfffea0f5cfa62bc01d |
| Linux/Linuxgeneric | 3.17 | Not reported |
Published upstream
Apr 22, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 5, 2026
In the Linux kernel, the following vulnerability has been resolved: driver core: platform: 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]
Quoted source text, attributed separately from HOL analysis.