You are using an out of date browser. It may not display this or other websites correctly. You should upgrade or use an alternative browser.
intel i915
About this tag
The intel i915 tag covers Linux kernel vulnerabilities and reliability fixes in Intel's integrated graphics driver, which is also relevant to Windows users running Linux in virtual machines, WSL, Azure, or dual-boot setups. Recent threads discuss CVEs such as CVE-2026-31767 (divide-by-zero in DSI display path), CVE-2026-31540 (NULL pointer dereference on suspend), CVE-2022-48893 (partial engine cleanup), and CVE-2023-52913 (use-after-free in context registration). These flaws typically cause crashes, resource leaks, or instability rather than remote code execution, but they highlight how display driver bugs can become security and reliability incidents in mixed-OS environments. The tag is useful for IT professionals and developers managing Intel graphics across platforms.
CVE-2026-31767 is a Linux kernel vulnerability published on May 1, 2026, affecting Intel’s i915 DSI display path, where a faulty Display Stream Compression timing adjustment can trigger a local divide-by-zero crash on certain systems. The bug is rated medium severity, not because it opens a...
CVE-2026-31540 is a Linux kernel i915 graphics-driver NULL pointer dereference, published on April 24, 2026, affecting Intel GPU systems where required i915 firmware is missing and suspend triggers an unchecked function-pointer call. It is not a Windows vulnerability in the usual Patch Tuesday...
The Linux kernel fix tracked as CVE-2022-48893 addresses a long-standing robustness gap in the Intel i915 DRM driver: when driver initialization aborts partway through GT/engine discovery, some engine structures could remain only partially initialized, leaving their cleanup hooks unset...
The Linux kernel’s graphics stack received a surgical but important fix addressing a potential use‑after‑free (UAF) in the Intel i915 driver: gem_context_register() could make a newly created context visible to userspace before the kernel had finished using the context pointer, opening a race...