CVE-2026-53115: Linux kernel · bus: fsl-mc: use generic driver_override infrastructure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in dbba371b19129abe9649553ab912e6bccf6c1a5b : update Linux kernel when convenient.
Data as of 26 Oct 2026, 14:05 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in dbba371b19129abe9649553ab912e6bccf6c1a5b, 8139ce66b52a4a5638bfb445b037c07d4abeb08e, 4911b836f35c034c36f102db4ecbe339b38e7d1d +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
Description
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]
References
- git.kernel.org/stable/c/dbba371b19129abe9649553ab912e6bccf6c1a5b (opens in a new tab)
- git.kernel.org/stable/c/4911b836f35c034c36f102db4ecbe339b38e7d1d (opens in a new tab)
- git.kernel.org/stable/c/8139ce66b52a4a5638bfb445b037c07d4abeb08e (opens in a new tab)
- git.kernel.org/stable/c/60bfb563a399c4597dc80588a1109758a8908b97 (opens in a new tab)
- git.kernel.org/stable/c/6c8dfb0362732bf1e4829867a2a5239fedc592d0 (opens in a new tab)