drm/xe/oa: Zero OA buffer at allocation
Impact
In the Linux kernel, the following vulnerability has been resolved:
Source excerpt · LinuxAffected packages
Affected products
Vendor version evidence. Product records are separate from automatic dependency matching.
Linux · Linux
Other versions: unaffected
| Version / range | Source status |
|---|---|
| 392bf22238ff88506f410c464ba0c7a84e9de471 to before 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9 | affected |
| 392bf22238ff88506f410c464ba0c7a84e9de471 to before cd3e2918c247db631d88cdd704596d9d27e5513e | affected |
| 392bf22238ff88506f410c464ba0c7a84e9de471 to before fd8662823caa114a63f07222d2aa448f6ac5e864 | affected |
Linux · Linux
Other versions: affected
| Version / range | Source status |
|---|---|
| 6.11 | affected |
| 0 to before 6.11 | unaffected |
| 6.18.59 through 6.18.* (inclusive) | unaffected |
| 7.2.13 through 7.2.* (inclusive) | unaffected |
| 7.3 through * (inclusive) | unaffected |
Original source 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)