SECUFOCUSNOW
Home›CVE index›CVE-2026-53118
Review reviewHigh

CVE-2026-53118

Linux Linux, linux kernel

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]

CVSS
7.8
EPSS
0.12%
2.08% 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: 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]

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 539fec78edb4e084e7c532affc56cc42d4ceea4b < 654ef9c33e138ede6734ac286282df9faf83cd11, >= 539fec78edb4e084e7c532affc56cc42d4ceea4b < fb5cb4913ce333cc4647722e8c2b8378e12f2464, >= 539fec78edb4e084e7c532affc56cc42d4ceea4b < 85bb534ff12aab6916058897b39c748940a7a4c6, >= 5.17, >= 5.17 < 6.18.33, >= 6.19 < 7.0.10
Fixed versions
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