Answer in brief
CVE-2026-53115 records a Unknown severity vulnerability in bus: fsl-mc: 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 | >=1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <dbba371b19129abe9649553ab912e6bccf6c1a5b || >=1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <4911b836f35c034c36f102db4ecbe339b38e7d1d || >=1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <8139ce66b52a4a5638bfb445b037c07d4abeb08e || >=1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <60bfb563a399c4597dc80588a1109758a8908b97 || >=1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <6c8dfb0362732bf1e4829867a2a5239fedc592d0 | dbba371b19129abe9649553ab912e6bccf6c1a5b, 4911b836f35c034c36f102db4ecbe339b38e7d1d, 8139ce66b52a4a5638bfb445b037c07d4abeb08e, 60bfb563a399c4597dc80588a1109758a8908b97, 6c8dfb0362732bf1e4829867a2a5239fedc592d0 |
| Linux/Linuxgeneric | 5.10 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: bus: fsl-mc: 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.