CVE-2026-53117
s390/cio: use generic driver_override infrastructure
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]
INFO
Published Date :
June 24, 2026, 5:17 p.m.
Last Modified :
July 23, 2026, 9:30 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS 3.1 | HIGH | [email protected] |
Solution
- Update the Linux kernel to include the fix.
- Ensure driver matching uses driver_override infrastructure.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53117.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53117 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53117
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53117 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53117 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jul. 23, 2026
Action Type Old Value New Value Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Added CWE CWE-416 Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.7 up to (excluding) 6.12.91 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.18.33 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.19 up to (excluding) 7.0.10 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.3 up to (excluding) 6.6.141 Added Reference Type kernel.org: https://git.kernel.org/stable/c/106d594711e97762788046c5bbb94f580abc4bf4 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/2081957d8c323ffb58a10bc64837717ac5a042a1 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/b660ba045b2b22cf3b4be72773de00cb48f47be5 Types: Patch Added Reference Type kernel.org: https://git.kernel.org/stable/c/c4295487124f461405e1ef64dfa8c4ab0cb7ebcf Types: Patch -
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'ebc3d179150347f3b6d97d8f249378bb2218f95e', 'lessThan': 'c4295487124f461405e1ef64dfa8c4ab0cb7ebcf', 'versionType': 'git'}, {'status': 'affected', 'version': 'ebc3d179150347f3b6d97d8f249378bb2218f95e', 'lessThan': '106d594711e97762788046c5bbb94f580abc4bf4', 'versionType': 'git'}, {'status': 'affected', 'version': 'ebc3d179150347f3b6d97d8f249378bb2218f95e', 'lessThan': '2081957d8c323ffb58a10bc64837717ac5a042a1', 'versionType': 'git'}, {'status': 'affected', 'version': 'ebc3d179150347f3b6d97d8f249378bb2218f95e', 'lessThan': 'b660ba045b2b22cf3b4be72773de00cb48f47be5', 'versionType': 'git'}, {'status': 'affected', 'version': 'ebc3d179150347f3b6d97d8f249378bb2218f95e', 'lessThan': 'ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4', 'versionType': 'git'}], 'programFiles': ['drivers/s390/cio/cio.h', 'drivers/s390/cio/css.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '5.3'}, {'status': 'unaffected', 'version': '0', 'lessThan': '5.3', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.141', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.91', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.33', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.10', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/s390/cio/cio.h', 'drivers/s390/cio/css.c'], 'defaultStatus': 'affected'}] Added 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] Added Reference https://git.kernel.org/stable/c/106d594711e97762788046c5bbb94f580abc4bf4 Added Reference https://git.kernel.org/stable/c/2081957d8c323ffb58a10bc64837717ac5a042a1 Added Reference https://git.kernel.org/stable/c/ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4 Added Reference https://git.kernel.org/stable/c/b660ba045b2b22cf3b4be72773de00cb48f47be5 Added Reference https://git.kernel.org/stable/c/c4295487124f461405e1ef64dfa8c4ab0cb7ebcf