Unknown severity · Source severity not reportedCVE-2026-98181

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

Answer in brief

CVE-2026-98181 records a Unknown severity vulnerability in drm/gud: fix out-of-bounds write in gud_plane_atomic_check(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 6, 2026Updated Oct 6, 2026Source checked Oct 6, 2026First seen by HOL Oct 6, 2026Material review Oct 6, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
Linux/Linuxgeneric	>=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <ee04903fe6a098160d20dde4fc5af4cb42846735 \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <4153a9e008f2512bd3cf90a319436865847369b9 \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <5f5e565410b4987e9663f599f9ab0c350f8338d4 \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <7e630edb22088df7aa0d55b02237a71e4c9a523d \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <2c92af27ad23e2fbc0367b11a9027d36d94ef4b3 \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <ea57100955c1c2a525ba1a98c18d9a05b25aeedb \|\| >=40e1a70b4aedf2859a1829991b48ef0ebe650bf2 <59ced288fcba9e91bd38e61a972ad782c4edb7d0	ee04903fe6a098160d20dde4fc5af4cb42846735, 4153a9e008f2512bd3cf90a319436865847369b9, 5f5e565410b4987e9663f599f9ab0c350f8338d4, 7e630edb22088df7aa0d55b02237a71e4c9a523d, 2c92af27ad23e2fbc0367b11a9027d36d94ef4b3, ea57100955c1c2a525ba1a98c18d9a05b25aeedb, 59ced288fcba9e91bd38e61a972ad782c4edb7d0
Linux/Linuxgeneric	5.13	Not reported

Recommended response

Check inventory. Check lockfiles and deployed manifests for Linux/Linux, Linux/Linux.
Review the reported fix. Update Linux/Linux to ee04903fe6a098160d20dde4fc5af4cb42846735 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 6, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.