Review reviewHigh

CVE-2026-53117

Linux Linux, linux kernel

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]

CVSS
7.8
EPSS
0.12%
2.38% percentile
CISA KEV
Not listed
Published
2026.06.25
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.12%
Technical severityCVSS 7.8

Vulnerability overview

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]

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= ebc3d179150347f3b6d97d8f249378bb2218f95e < c4295487124f461405e1ef64dfa8c4ab0cb7ebcf, >= ebc3d179150347f3b6d97d8f249378bb2218f95e < 106d594711e97762788046c5bbb94f580abc4bf4, >= ebc3d179150347f3b6d97d8f249378bb2218f95e < 2081957d8c323ffb58a10bc64837717ac5a042a1, >= ebc3d179150347f3b6d97d8f249378bb2218f95e < b660ba045b2b22cf3b4be72773de00cb48f47be5, >= ebc3d179150347f3b6d97d8f249378bb2218f95e < ac4d8bb6e2e13e8684a76ea48d13ebaaaf5c24c4, >= 5.3, >= 5.3 < 6.6.141, >= 6.7 < 6.12.91, >= 6.13 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
6.6.141, 6.12.91, 6.18.33, 7.0.10

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-416
CVE-2026-53117 — Linux Linux, linux kernel | SECUFOCUS NOW