Review reviewHigh

CVE-2025-71099

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free. Fix this by caching the id in a local variable while holding the lock. v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_conf...

CVSS
7.8
EPSS
0.11%
1.82% percentile
CISA KEV
Not listed
Published
2026.01.14
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

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

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl() In xe_oa_add_config_ioctl(), we accessed oa_config->id after dropping metrics_lock. Since this lock protects the lifetime of oa_config, an attacker could guess the id and call xe_oa_remove_config_ioctl() with perfect timing, freeing oa_config before we dereference it, leading to a potential use-after-free. Fix this by caching the id in a local variable while holding the lock. v2: (Matt A) - Dropped mutex_unlock(&oa->metrics_lock) ordering change from xe_oa_remove_conf...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 < c6d30b65b7a44dac52ad49513268adbf19eab4a2, >= cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 < 7cdb9a9da935c687563cc682155461fef5f9b48d, >= cdf02fe1a94a768cbcd20f5c4e1a1d805f4a06c0 < dcb171931954c51a1a7250d558f02b8f36570783, >= 6.11, >= 6.11.1 < 6.12.64, >= 6.13 < 6.18.4, 6.11, 6.19
Fixed versions
6.12.64, 6.18.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