# CVE-2026-68262: drm/imagination: Fix user array stride in pvr_set_uobj_array()

> A stride calculation error in the Imagination DRM driver causes memory corruption, potentially allowing local attackers to execute code or escalate privileges.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 17 Aug 2026
- **Also known as:** BELL-CVE-2026-68262, DEBIAN-CVE-2026-68262, GHSA-8f87-qjgg-4j6v, UBUNTU-CVE-2026-68262

## What is CVE-2026-68262?

CVE-2026-68262 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 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/imagination: Fix user array stride in pvr_set_uobj_array()

pvr_set_uobj_array() copies an array of kernel objects to a userspace
array whose element size is described by out->stride. When out->stride
is different from the kernel object size, the slow path advances the
userspace pointer by the kernel object size and the kernel pointer by the
userspace stride.

This reverses the intended layout. For larger userspace strides, later
copies read from the wrong kernel addresses. For smaller userspace
strides, later copies are written at the wrong userspace offsets. The
padding clear is also done only for the first element instead of the
padding area for each element.

Advance the userspace pointer by out->stride and the kernel pointer by
obj_size, and clear per-element padding while the current userspace
pointer is still available.

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


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

Apply the vendor's patch.

## Is CVE-2026-68262 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-68262 is a high-severity memory corruption vulnerability in Linux, published on 10 Aug 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-68262 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-68262/ (Markdown: https://insights.sbomify.com/CVE-2026-68262/index.md)
```

## Sources

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

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