Answer in brief
CVE-2026-53118 records a Unknown severity vulnerability in vdpa: 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 | 5.17 | Not reported |
| Linux/Linuxgeneric | >=539fec78edb4e084e7c532affc56cc42d4ceea4b <4005cb89139f7c9af85046b241dcf3fa2e1b3559 || >=539fec78edb4e084e7c532affc56cc42d4ceea4b <4eab1a74a498f0bf19f102f9362e9deef9307aea || >=539fec78edb4e084e7c532affc56cc42d4ceea4b <654ef9c33e138ede6734ac286282df9faf83cd11 || >=539fec78edb4e084e7c532affc56cc42d4ceea4b <fb5cb4913ce333cc4647722e8c2b8378e12f2464 || >=539fec78edb4e084e7c532affc56cc42d4ceea4b <85bb534ff12aab6916058897b39c748940a7a4c6 | 4005cb89139f7c9af85046b241dcf3fa2e1b3559, 4eab1a74a498f0bf19f102f9362e9deef9307aea, 654ef9c33e138ede6734ac286282df9faf83cd11, fb5cb4913ce333cc4647722e8c2b8378e12f2464, 85bb534ff12aab6916058897b39c748940a7a4c6 |
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: vdpa: 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.