SECUFOCUSNOW
Home›CVE index›CVE-2023-53552
Review reviewHigh

CVE-2023-53552

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/i915: mark requests for GuC virtual engines to avoid use-after-free References to i915_requests may be trapped by userspace inside a sync_file or dmabuf (dma-resv) and held indefinitely across different proceses. To counter-act the memory leaks, we try to not to keep references from the request past their completion. On the other side on fence release we need to know if rq->engine is valid and points to hw engine (true for non-virtual requests). To make it possible extra bit has been added to rq->execution_mask, for mar...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.10.05
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: drm/i915: mark requests for GuC virtual engines to avoid use-after-free References to i915_requests may be trapped by userspace inside a sync_file or dmabuf (dma-resv) and held indefinitely across different proceses. To counter-act the memory leaks, we try to not to keep references from the request past their completion. On the other side on fence release we need to know if rq->engine is valid and points to hw engine (true for non-virtual requests). To make it possible extra bit has been added to rq->execution_mask, for mar...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= bcb9aa45d5a0e11ef91245330c53cde214d15e8d < 8017a27cec32eac8c8f9430b0a3055840136b856, >= bcb9aa45d5a0e11ef91245330c53cde214d15e8d < 7fb464d52fa41c31a6fd1ad82888e67c65935d94, >= bcb9aa45d5a0e11ef91245330c53cde214d15e8d < 5eefc5307c983b59344a4cb89009819f580c84fa, >= 6.0, >= 6.0 < 6.1.54, >= 6.2 < 6.5.4
Fixed versions
6.1.54, 6.5.4

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