Answer in brief
CVE-2026-53120 records a Unknown severity vulnerability in PCI: 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 | >=782a985d7af26db39e86070d28f987cad21313c0 <fdfa287956d00b936e0ac409b21e4f90501ad109 || >=782a985d7af26db39e86070d28f987cad21313c0 <dfe950d9464cad609f3b118c6203e2708055bc61 || >=782a985d7af26db39e86070d28f987cad21313c0 <58a42be0d70307d765594fc581f5f5e5ef059712 || >=782a985d7af26db39e86070d28f987cad21313c0 <c5b2c5755495507e14f310c2653c85de0a309b1f || >=782a985d7af26db39e86070d28f987cad21313c0 <10a4206a24013be4d558d476010cbf2eb4c9fa64 | fdfa287956d00b936e0ac409b21e4f90501ad109, dfe950d9464cad609f3b118c6203e2708055bc61, 58a42be0d70307d765594fc581f5f5e5ef059712, c5b2c5755495507e14f310c2653c85de0a309b1f, 10a4206a24013be4d558d476010cbf2eb4c9fa64 |
| Linux/Linuxgeneric | 3.16 | 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: 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]
Quoted source text, attributed separately from HOL analysis.