Copyright © 2012 Red Hat, Inc. All rights reserved. Moderate 2026-10-06T00:00:00 kernel: drm/gud: fix out-of-bounds write in gud_plane_atomic_check() 4.6 CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CWE-787

In the Linux kernel, the following vulnerability has been resolved: drm/gud: fix out-of-bounds write in gud_plane_atomic_check() The plane property loop uses req->properties[num_properties + i] as write index while simultaneously incrementing `num_properties` inside the loop. At iteration i, num_properties has also incremented by i, so the write is done at `initial_num_properties + 2*i`, skipping every other index and advancing by 2 per iteration. With just 2 connector and 32 plane properties the last write happens at index 64, one slot past the end of the 64-slot (indices 0–63) allocation. A USB device can trigger OOB by advertising the maximum number of properties. Fix by dropping the redundant `+ i`; num_properties is already the correct running index, as gud_connector_fill_properties() fills the preceding slots.

A flaw was found in the Linux kernel's Generic USB Display (GUD) driver. An attacker connecting a specially crafted USB device advertising a maximum number of display properties can trigger an array indexing error during property validation. This flaw leads to an out-of-bounds memory write, which can result in a system crash causing a Denial of Service (DoS) or potentially lead to arbitrary code execution.

An out of bounds kernel write in the DRM GUD USB display driver occurs because gud_plane_atomic_check uses num_properties plus i as the property array index while num_properties is also incremented in the same loop. A malicious USB display device can advertise enough connector and plane properties to make the driver write past the end of the allocated request property array. For the CVSS the PR:N because the attacker does not need an account or privileges on the target system but must connect or control a malicious physical USB device. The attack vector is AV:P and is not network reachable in the normal deployment model. The base impact is local denial of service or limited memory corruption. The paranoid impact includes potential confidentiality integrity and availability compromise because this is a kernel heap out of bounds write and should be reviewed manually. Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Red Hat Enterprise Linux 10 Fix deferred kernel Red Hat Enterprise Linux 6 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel Red Hat Enterprise Linux 7 Not affected kernel-rt Red Hat Enterprise Linux 8 Not affected kernel Red Hat Enterprise Linux 8 Not affected kernel-rt Red Hat Enterprise Linux 9 Fix deferred kernel Red Hat Enterprise Linux 9 Fix deferred kernel-rt Red Hat OpenShift Container Platform 4 Not affected openshift/ose-rhel-coreos-8 Red Hat OpenShift Container Platform 4 Fix deferred openshift/ose-rhel-coreos-9 https://www.cve.org/CVERecord?id=CVE-2026-98181 https://nvd.nist.gov/vuln/detail/CVE-2026-98181 https://git.kernel.org/pub/scm/linux/security/vulns.git/plain/cve/published/2026/CVE-2026-98181.mbox