# CVE-2026-74417: drm/radeon: fix integer overflow in radeon_align_pitch()

> An integer overflow in the Radeon DRM driver can cause invalid buffer allocations, potentially leading to denial of service.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 15 Aug 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BELL-CVE-2026-74417, DEBIAN-CVE-2026-74417, GHSA-h36j-68r7-9j5g, UBUNTU-CVE-2026-74417

## What is CVE-2026-74417?

CVE-2026-74417 is a high-severity vulnerability in Linux, published on 15 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/radeon: fix integer overflow in radeon_align_pitch()

radeon_align_pitch() has the same kind of overflow issue as the old
amdgpu helper: both the alignment round-up add and the final
'aligned * cpp' calculation can overflow signed int.

If that wraps, radeon_mode_dumb_create() can end up returning an
invalid pitch or creating a zero-sized dumb buffer.

Fix this by using check_add_overflow() for the alignment round-up and
check_mul_overflow() for the final pitch calculation, returning 0 on
overflow. Also reject zero pitch and size in
radeon_mode_dumb_create().

Found via AST-based call-graph analysis using sqry.

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


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

Apply the vendor's patch.

## Is CVE-2026-74417 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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