# CVE-2026-80740: drm/log: Fix infinite loop when scale is too large for display

> A local attacker can cause a denial of service in the Linux kernel via an infinite loop in the DRM log driver when handling large font scales.

- **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:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** BELL-CVE-2026-80740, DEBIAN-CVE-2026-80740, GHSA-pw7c-6m3h-4wvr, UBUNTU-CVE-2026-80740

## What is CVE-2026-80740?

CVE-2026-80740 is a denial of service vulnerability in Linux, published on 3 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:

drm/log: Fix infinite loop when scale is too large for display

When scale is large enough that scaled_font exceeds the display
dimensions, rows or columns become 0. A columns value of 0 causes
an infinite loop in drm_log_draw_kmsg_record() because the loop
never decrements len.

Check for zero rows/columns in drm_log_setup_modeset() and return
an error, cleaning up the already allocated buffer to avoid a leak.

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


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

Apply the vendor's patch.

## Is CVE-2026-80740 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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