CVE-2026-74417

Received Received - Intake

Integer Overflow in Linux Kernel Radeon Driver

Publication date: 2026-08-15

Last updated on: 2026-08-17

Assigner: kernel.org

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-15

Last Modified

2026-08-17

Generated

2026-09-04

AI Q&A

2026-08-15

EPSS Evaluated

2026-09-03

NVD

CVE-2026-74417

EUVD

EUVD-2026-59564

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This vulnerability is in the Linux kernel's drm/radeon driver. It involves an integer overflow in the radeon_align_pitch() function. The overflow can occur during alignment calculations and final pitch computations, potentially leading to invalid or zero-sized buffer creation in radeon_mode_dumb_create().

Detection Guidance

This vulnerability is specific to the Linux kernel's drm/radeon driver and involves integer overflow in the radeon_align_pitch() function. Detection requires checking the kernel version and the presence of the vulnerable code path. Use uname -a to check your kernel version and grep for the radeon driver in your kernel logs or configuration.

Impact Analysis

If exploited, this flaw could allow an attacker to cause system instability or crashes by triggering invalid memory operations. It may also lead to denial-of-service conditions or unexpected behavior in graphics operations.

Compliance Impact

This vulnerability does not directly affect compliance with GDPR, HIPAA, or similar standards as it is a low-level kernel memory handling issue in the Radeon graphics driver. Compliance risks would only arise if exploitation led to system instability or data corruption, which is not indicated in the provided context.

Mitigation Strategies

Apply the latest kernel update provided by your Linux distribution to patch the vulnerability. If an update is not immediately available, consider disabling the radeon driver if not in use by blacklisting the module or restricting access to GPU functionality.

Hi! I’m here to help you understand CVE-2026-74417. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70