---
id: CVE-2026-53115
title: 'bus: fsl-mc: use generic driver_override infrastructure'
summary: |-
  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 …
severity: none
vendor: Linux
product: Linux
affected:
  - >-
    Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <
    dbba371b19129abe9649553ab912e6bccf6c1a5b
  - >-
    Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <
    4911b836f35c034c36f102db4ecbe339b38e7d1d
  - >-
    Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <
    8139ce66b52a4a5638bfb445b037c07d4abeb08e
  - >-
    Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <
    60bfb563a399c4597dc80588a1109758a8908b97
  - >-
    Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d <
    6c8dfb0362732bf1e4829867a2a5239fedc592d0
  - Linux 5.10
published: '2026-06-24'
updated: '2026-10-21'
sourceUpdated: '2026-10-21T12:42:05.258Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-53115'
references:
  - url: 'https://git.kernel.org/stable/c/dbba371b19129abe9649553ab912e6bccf6c1a5b'
  - url: 'https://git.kernel.org/stable/c/4911b836f35c034c36f102db4ecbe339b38e7d1d'
  - url: 'https://git.kernel.org/stable/c/8139ce66b52a4a5638bfb445b037c07d4abeb08e'
  - url: 'https://git.kernel.org/stable/c/60bfb563a399c4597dc80588a1109758a8908b97'
  - url: 'https://git.kernel.org/stable/c/6c8dfb0362732bf1e4829867a2a5239fedc592d0'
tags:
  - cve.org
epss: 0.00175
epssPercentile: 0.06606
ingestedAt: '2026-10-21T12:48:53.622Z'
---

## Overview

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]

## Affected

- `Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d < dbba371b19129abe9649553ab912e6bccf6c1a5b`
- `Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d < 4911b836f35c034c36f102db4ecbe339b38e7d1d`
- `Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d < 8139ce66b52a4a5638bfb445b037c07d4abeb08e`
- `Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d < 60bfb563a399c4597dc80588a1109758a8908b97`
- `Linux >= 1f86a00c1159fd77e66b1bd6ff1a183f4d46f34d < 6c8dfb0362732bf1e4829867a2a5239fedc592d0`
- `Linux 5.10`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.