CVE-2026-53117: Linux kernel · s390/cio: use generic driver_override infrastructure
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in c4295487124f461405e1ef64dfa8c4ab0cb7ebcf : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in c4295487124f461405e1ef64dfa8c4ab0cb7ebcf, b660ba045b2b22cf3b4be72773de00cb48f47be5, ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 6 Nov 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: 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]
References
- git.kernel.org/stable/c/c4295487124f461405e1ef64dfa8c4ab0cb7ebcf (opens in a new tab)
- git.kernel.org/stable/c/106d594711e97762788046c5bbb94f580abc4bf4 (opens in a new tab)
- git.kernel.org/stable/c/2081957d8c323ffb58a10bc64837717ac5a042a1 (opens in a new tab)
- git.kernel.org/stable/c/b660ba045b2b22cf3b4be72773de00cb48f47be5 (opens in a new tab)
- git.kernel.org/stable/c/ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 (opens in a new tab)