Technical impact
In the Linux kernel, a bug in the handling of ttm_bo_type_kernel buffer objects meant that newly allocated buffers were not guaranteed to be zeroed, and because the OA buffer can be exposed to user space via mmap, residual data from previously freed memory could be read by a process with access to the DRM device, allowing an attacker who can request an OA buffer with the DRM_XE_OA_PROPERTY_OA_DISABLED property to obtain stale kernel memory contents and potentially leak sensitive information such as cryptographic keys.
Affected Systems
All Linux kernel releases that include the drm/xe/oa component without the zero‑initialization fix—specifically versions prior to the commit that added zeroing of the OA buffer (commit 126c4c5388f9311a390b9b254a835b0cf0f55331)—are affected, regardless of vendor.
Risk and Exploitability
The attack vector requires the ability to open a DRM device and create a stream with the OA_DISABLED property, which is typically available to users with permission to interact with the DRM subsystem; once the buffer is mapped, the attacker can read uninitialized memory and recover information, representing a to high risk for systems exposing DRM devices to unprivileged users. The CVSS score is 5.5, and the EPSS score is < 1%; a public exploit has not been reported in the CISA KEV catalog, so the exact likelihood is uncertain but the vulnerability remains theoretically exploitable under the described conditions.