All vulnerabilities
CVE-2026-99208

Linux: drm/xe/oa: Zero OA buffer at allocation

Linux LinuxOperating systems
Open in ThreatlineRecord JSON
CVSS
NoneNot scored
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)No scoreNo FIRST EPSS score in this snapshot yet
Fixed in21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9Fixed versionCVE List
Published28 Oct 2026Updated 28 Oct 2026CVE List

What fixes it

  • 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9LinuxCVE List

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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)

Text from CVE List

Affected versions 8

  • Linuxaffected: 392bf22238ff88506f410c464ba0c7a84e9de471 before 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9CVE List
  • Linuxaffected: 392bf22238ff88506f410c464ba0c7a84e9de471 before cd3e2918c247db631d88cdd704596d9d27e5513eCVE List
  • Linuxaffected: 392bf22238ff88506f410c464ba0c7a84e9de471 before fd8662823caa114a63f07222d2aa448f6ac5e864CVE List
  • Linuxaffected: 6.11CVE List
  • Linuxunaffected: all versions before 6.11CVE List
  • Linuxunaffected: 6.18.59 through 6.18.*CVE List
  • Linuxunaffected: 7.2.13 through 7.2.*CVE List
  • Linuxunaffected: 7.3CVE List

References 3