CVE-2026-53120: Linux kernel · PCI: use generic driver_override infrastructure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in fdfa287956d00b936e0ac409b21e4f90501ad109 : 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 fdfa287956d00b936e0ac409b21e4f90501ad109, dfe950d9464cad609f3b118c6203e2708055bc61, c5b2c5755495507e14f310c2653c85de0a309b1f +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: PCI: 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/fdfa287956d00b936e0ac409b21e4f90501ad109 (opens in a new tab)
- git.kernel.org/stable/c/dfe950d9464cad609f3b118c6203e2708055bc61 (opens in a new tab)
- git.kernel.org/stable/c/58a42be0d70307d765594fc581f5f5e5ef059712 (opens in a new tab)
- git.kernel.org/stable/c/c5b2c5755495507e14f310c2653c85de0a309b1f (opens in a new tab)
- git.kernel.org/stable/c/10a4206a24013be4d558d476010cbf2eb4c9fa64 (opens in a new tab)