28 matches found
CVE-2025-32091
CVE-2025-32091 affects Intel Arc B-series GPUs in Ring 1: Device Drivers. The issue is incorrect default permissions in firmware that may allow local privilege escalation by a system software adversary with privileged user access and low attack complexity, requiring no user interaction. Impacts a...
CVE-2025-25216
Improper input validation in some firmware for some IntelR Graphics Drivers and Intel LTS kernels within Ring 1: Device Drivers may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a low complexity attack may enable denial of service. This result...
CVE-2025-25216
CVE-2025-25216 involves improper input validation in Intel graphics firmware and Intel LTS kernels within Ring 1: Device Drivers, enabling a local, low-complexity DoS by an authenticated, unprivileged user. Red Hat and ENISA entries confirm the same issue affecting Intel Arc graphics family and r...
PT-2025-46429
Name of the Vulnerable Software and Affected Versions Intel Arc B-series GPUs affected versions not specified Description A configuration issue with default permissions in some firmware for Intel Arc B-series GPUs within Ring 1 device drivers may allow an attacker to gain elevated privileges. A...
Intel® Graphics Advisory
Summary: Potential security vulnerabilities for some Intel® Graphics software may allow escalation of privilege or denial of service. Intel is releasing software updates to mitigate these potential vulnerabilities. Vulnerability Details: CVEID: CVE-2025-32091 Description: Incorrect default...
SUSE CVE-2021-28689
x86: Speculative vulnerabilities with bare non-shim 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to...
UBUNTU-CVE-2021-28689
x86: Speculative vulnerabilities with bare non-shim 32-bit PV guests 32-bit x86 PV guest kernels run in ring 1. At the time when Xen was developed, this area of the i386 architecture was rarely used, which is why Xen was able to use it to implement paravirtualisation, Xen's novel approach to...
kernel: xen: hypercalls exposed to privilege rings 1 and 2 of HVM guests
Xen 3.0.3 through 4.1.x possibly 4.1.6.1, 4.2.x possibly 4.2.3, and 4.3.x possibly 4.3.1 does not properly prevent access to hypercalls, which allows local guest users to gain privileges via a crafted application running in ring 1 or 2...