VulnerabilityPublished 28 Oct 2026

CVE-2026-99208: Linux kernel · drm/xe/oa: Zero OA buffer at allocation

Affects Linux kernelSource CVE Database V5

Not known to be exploited · fixed in fd8662823caa114a63f07222d2aa448f6ac5e864 : update Linux kernel when convenient.

Data as of 28 Oct 2026, 10:58 UTC

Severity

Unrated

Rated by Threat Radar · CVSS not yet scored by NVD

Patch: Available – fixed in fd8662823caa114a63f07222d2aa448f6ac5e864, cd3e2918c247db631d88cdd704596d9d27e5513e, 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade Linux kernel to fd8662823caa114a63f07222d2aa448f6ac5e864, cd3e2918c247db631d88cdd704596d9d27e5513e or 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9.

Affected software

Product	Affected	Fixed in
LinuxLinux	Affected ≥ 392bf22238ff88506f410c464ba0c7a84e9de471, < fd8662823caa114a63f07222d2aa448f6ac5e864	Fixed in fd8662823caa114a63f07222d2aa448f6ac5e864
LinuxLinux	Affected ≥ 392bf22238ff88506f410c464ba0c7a84e9de471, < cd3e2918c247db631d88cdd704596d9d27e5513e	Fixed in cd3e2918c247db631d88cdd704596d9d27e5513e
LinuxLinux	Affected ≥ 392bf22238ff88506f410c464ba0c7a84e9de471, < 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9	Fixed in 21f41b6daf0dbe2cdaaf9f54af6e23fd3c9190b9
LinuxLinux	Affected =6.11	Fixed in–
Linuxlinux/kernel`pkg:deb/linux/kernel`Other threats	Affected =6.11	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

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)

References

Community reviews

Loading reviews…