# CVE-2026-98566: drm/imagination: clamp freelist reconstruction requests

> A missing bounds check in the Imagination DRM driver allows an attacker to trigger memory corruption via crafted firmware reconstruction requests.

- **Severity:** Not scored
- **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:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** BELL-CVE-2026-98566, DEBIAN-CVE-2026-98566, GHSA-8m42-mvgx-m6jp, UBUNTU-CVE-2026-98566

## What is CVE-2026-98566?

CVE-2026-98566 is a vulnerability in Linux, published on 18 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/imagination: clamp freelist reconstruction requests

The firmware reconstruction count controls accesses to the request's
fixed freelist ID array and the copy into the fixed response array.
Neither access currently bounds the count to those protocol arrays.

Clamp the count to the request capacity, which is shared by the response
layout, and use that count consistently for reconstruction and response
publication. Keep the firmware recovery exchange instead of dropping an
oversized request without a response, as discussed with the firmware
maintainer.

The issue was found by our static-analysis tool.

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


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

Apply the vendor's patch.

## Is CVE-2026-98566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98566 is a vulnerability in Linux, published on 18 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-98566 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-98566/ (Markdown: https://insights.sbomify.com/CVE-2026-98566/index.md)
```

## Sources

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

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