Description
In the Linux kernel, the following vulnerability has been resolved: drm/xe/oa: Zero OA buffer at allocation ttm_bo_type_kernel BOs are not guaranteed to be zeroed on allocation and may contain data from previously freed pages. Since the OA buffer is mmap'able by userspace, this can expose stale kernel memory contents. Streams opened with DRM_XE_OA_PROPERTY_OA_DISABLED allocate the OA buffer without calling xe_oa_init_oa_buffer(). Zero the buffer at allocation to prevent information disclosure through mmap. The existing zeroing in xe_oa_init_oa_buffer() remains necessary for zero report-id/timestamp detection on enable/re-enable. (cherry picked from commit 126c4c5388f9311a390b9b254a835b0cf0f55331)
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
Linux Linux
Default version status: unaffected
392bf22238ff88506f410c464ba0c7a84e9de471 to < 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9affected392bf22238ff88506f410c464ba0c7a84e9de471 to < cd3e2918c247db631d88cdd704596d9d27e5513eaffected392bf22238ff88506f410c464ba0c7a84e9de471 to < fd8662823caa114a63f07222d2aa448f6ac5e864affected
Linux Linux
Default version status: affected
6.11affected0 to < 6.11unaffected6.18.59 to ≤ 6.18.*unaffected7.2.13 to ≤ 7.2.*unaffected7.3 to ≤ *unaffected