Back

HIGH

drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()

Published Jan 13, 2026

Description

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_config_ioctl()

(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)

Affected products

Remediation

Red Hat statement

Exploitation requires precise timing to win the race between add and remove config ioctls. This requires access to the Xe DRM device, typically available to video group users. The fix caches the id locally while holding the lock.

Metrics

References (8)

Change history (0)

No recorded changes yet.

Sources
CVE.org / MITRE
Status PUBLISHED
Assigner Linux
Published Jan 13, 2026
Updated Aug 5, 2026
Reserved Jan 13, 2026
NVD
Status Modified
Modified Jul 30, 2026
Red Hat
Severity Low
Public date Jan 13, 2026