# CVE-2026-90245: fbdev: kyro: Validate overlay viewport coordinates

> A local attacker can trigger integer overflows in the Kyro framebuffer driver, potentially causing system instability or denial of service.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102891, BELL-CVE-2026-90245, DEBIAN-CVE-2026-90245, GHSA-74pp-fw2v-5w87, UBUNTU-CVE-2026-90245

## What is CVE-2026-90245?

CVE-2026-90245 is a vulnerability in Linux, published on 17 Sep 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:

fbdev: kyro: Validate overlay viewport coordinates

The overlay viewport end coordinates are computed from the viewport
origin and dimensions using 32-bit unsigned arithmetic. Large input
values can cause these calculations to wrap around before the resulting
coordinates are passed to SetOverlayViewPort().

SetOverlayViewPort() packs the viewport coordinates into 16-bit
register fields. The X coordinates are additionally adjusted by +2
and +1 before being written. Validate the coordinate calculations
for 32-bit wraparound and ensure that the adjusted coordinates fit
within their 16-bit register fields before calling
SetOverlayViewPort().

Found by Linux Verification Center (linuxtesting.org) with SVACE.

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


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

Apply the vendor's patch.

## Is CVE-2026-90245 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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