This entry references a vulnerability identified as CVE-2026-99632 related to the DRM amdkfd component, specifically involving the use of the queue's process information for the WPTR BO eviction fence. The description provided does not include technical details about the nature of the vulnerability or its impact. The affected versions are exactly 3.0 and 4.0. No CVSS score or detailed impact information is available.
This entry references a vulnerability identified as CVE-2026-99629 related to the drm/amdgpu driver component, specifically involving the clearing of the RB_OVERFLOW bit when enabling interrupts for navi10_ih. The description provided does not include technical details about the flaw, its impact, or exploitation. The affected product is Microsoft software with versions 3.0 and 4.0 noted. No CVSS score or detailed impact information is available.
This vulnerability, identified as CVE-2026-99736, relates to the accounting of swapin-error markers in Microsoft software versions 3.0 and 4.0. The published information is limited and does not provide details on the nature or impact of the flaw. No CVSS score or exploit information is available.
This vulnerability, identified as CVE-2026-99628, relates to the drm/amd/display component and involves improper handling of DDC pins, specifically closing pins that are not owned. The advisory references Microsoft as the vendor and lists affected versions 3.0 and 4.0. No detailed technical impact or exploitation information is provided.
This vulnerability, identified as CVE-2026-99735, relates to improper use of stack pointers when walking PUD and PMD tables in Microsoft software versions 3.0 and 4.0. The advisory does not provide detailed technical information or impact specifics. No CVSS score or exploit information is available.
This vulnerability involves the mm/shmem component where the function shmem_file() needs to verify the file's inode. The advisory provides no further technical details or impact information.
CVE-2026-99732 is a vulnerability related to the mm/filemap component in Microsoft software versions 3.0 and 4.0. The issue involves reading mapping->a_ops->free_folio under i_lock, but no detailed technical or impact information is provided.
This vulnerability, identified as CVE-2026-99625, relates to the drm/amdgpu component and involves fixing duplicate dependency fence releases. The advisory references Microsoft's support lifecycle but provides no detailed technical or impact information. The affected versions are exactly 3.0 and 4.0. No CVSS score or exploit information is available.
CVE-2026-99731 is a vulnerability in Microsoft software versions 3.0 and 4.0 related to the mm/filemap component, specifically concerning the handling of folio lock wakeups when interrupted by signals. The advisory provides no further technical details or impact description.
This vulnerability relates to the drm/amdgpu component where the system attempts to walk command submission (CS) chunks even after their allocation has failed. The issue is identified in Microsoft products with affected versions 3.0 and 4.0. No CVSS score or detailed impact information is provided.
This vulnerability, identified as CVE-2026-99619, involves the drm/amdgpu component where the gang dependency fence is dropped twice. The issue affects Microsoft products specifically versions 3.0 and 4.0. No CVSS score or detailed impact information is provided, and there are no known exploits in the wild.
A vulnerability in the nvmet component causes it to return memory contents beyond valid data when reading the ANA log page. This could potentially expose unintended memory data. The affected versions are 3.0 and 4.0. No CVSS score or detailed impact information is provided.
This vulnerability involves the validation of /dev/mem mmap ranges on arm64 architectures to prevent overflow issues. It affects specific Microsoft software versions 3.0 and 4.0. No detailed impact or exploitation information is provided.
CVE-2026-99616 is a vulnerability identified in Microsoft products version 3.0 and 4.0. The provided information does not include technical details about the nature of the vulnerability or its impact. No CVSS score or exploit information is available.