CVE-2026-98181: Linux kernel · drm/gud: fix out-of-bounds write in gud_plane_atomic_check()
Affects Linux kernelSource GCVE Database
Not known to be exploited.
Data as of 28 Oct 2026, 01:27 UTC
Rated by Threat Radar · CVSS not yet scored by NVD
Exploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.04 LTSlinuxpkg:deb/ubuntu/linux?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-awspkg:deb/ubuntu/linux-aws?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azurepkg:deb/ubuntu/linux-azure?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-azure-fdepkg:deb/ubuntu/linux-azure-fde?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gcppkg:deb/ubuntu/linux-gcp?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSlinux-gkepkg:deb/ubuntu/linux-gke?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
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.
References
- ubuntu.com/security/CVE-2026-98181 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-98181 (opens in a new tab)
- git.kernel.org/linus/59ced288fcba9e91bd38e61a972ad782c4edb7d0 (opens in a new tab)
- git.kernel.org/stable/c/2c92af27ad23e2fbc0367b11a9027d36d94ef4b3 (opens in a new tab)
- git.kernel.org/stable/c/4153a9e008f2512bd3cf90a319436865847369b9 (opens in a new tab)
- git.kernel.org/stable/c/59ced288fcba9e91bd38e61a972ad782c4edb7d0 (opens in a new tab)
- git.kernel.org/stable/c/5f5e565410b4987e9663f599f9ab0c350f8338d4 (opens in a new tab)
- git.kernel.org/stable/c/7e630edb22088df7aa0d55b02237a71e4c9a523d (opens in a new tab)
- git.kernel.org/stable/c/ea57100955c1c2a525ba1a98c18d9a05b25aeedb (opens in a new tab)
- git.kernel.org/stable/c/ee04903fe6a098160d20dde4fc5af4cb42846735 (opens in a new tab)