← Back to CVE intelligence
CVE intelligence

CVE-2026-99208

Vulnerability intelligence

Published Oct 28, 2026Sources checked Nov 20, 2026
N/ACVSS not listedScore unavailable
What this means

Review the available evidence

CVE-2026-99208. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

Vendor revision: Nov 20, 2026

Release Notes

Vendor-listed releases

  • 0:6.18.62-1.1.azl4

Ubuntu Security Notices guidance

Vendor revision: Nov 19, 2026
Vendor remediation details

This update corrects flaws in the following subsystems: - S390 architecture; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Compute Acceleration Framework; - FireWire subsystem; - GPIO subsystem; - GPU drivers; - Microsoft Hyper-V drivers; - I2C subsystem; - Multiple devices driver; - Network drivers; - STMicroelectronics network drivers; - Power supply drivers; - S/390 drivers; - SCSI subsystem; - SPI subsystem; - TCM subsystem; - UFS subsystem; - File systems infrastructure; - Ext4 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - Tracing file system; - XFS file system; - Kernel futex primitives; - Key management; - Key Management; - VMware vSockets driver; - io_uring subsystem; - IPC subsys

CISA KEVNot listedBased on the latest collected catalog
EPSS0.2%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-99208?

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)

Source: NVD