Answer in brief
CVE-2026-53117 records a Unknown severity vulnerability in s390/cio: 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 | >=ebc3d179150347f3b6d97d8f249378bb2218f95e <c4295487124f461405e1ef64dfa8c4ab0cb7ebcf || >=ebc3d179150347f3b6d97d8f249378bb2218f95e <106d594711e97762788046c5bbb94f580abc4bf4 || >=ebc3d179150347f3b6d97d8f249378bb2218f95e <2081957d8c323ffb58a10bc64837717ac5a042a1 || >=ebc3d179150347f3b6d97d8f249378bb2218f95e <b660ba045b2b22cf3b4be72773de00cb48f47be5 || >=ebc3d179150347f3b6d97d8f249378bb2218f95e <ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 | c4295487124f461405e1ef64dfa8c4ab0cb7ebcf, 106d594711e97762788046c5bbb94f580abc4bf4, 2081957d8c323ffb58a10bc64837717ac5a042a1, b660ba045b2b22cf3b4be72773de00cb48f47be5, ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 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: s390/cio: 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.