# CVE-2026-98181: drm/gud: fix out-of-bounds write in gud_plane_atomic_check()

> A malicious USB device can trigger an out-of-bounds write in the Linux kernel DRM driver, potentially leading to code execution or system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106404, BELL-CVE-2026-98181, DEBIAN-CVE-2026-98181, GHSA-mrf5-p4fw-fr76, UBUNTU-CVE-2026-98181

## What is CVE-2026-98181?

CVE-2026-98181 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

## Which versions are affected by CVE-2026-98181?


## How do I fix CVE-2026-98181?

Apply the vendor's patch.

## Is CVE-2026-98181 being exploited?

There is no known exploitation of CVE-2026-98181 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98181 and fix it if it is affected.

What it is: CVE-2026-98181 is a memory corruption vulnerability in Linux, published on 6 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98181 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98181/ (Markdown: https://insights.sbomify.com/CVE-2026-98181/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98181
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98181
- OSV: https://osv.dev/vulnerability/CVE-2026-98181

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98181/
Summaries are generated and may contain mistakes; the official description above is the record.