From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-74417: drm/radeon: fix integer overflow in radeon_align_pitch()
Date: Sat, 15 Aug 2026 15:12:24 +0900 [thread overview]
Message-ID: <2026081512-CVE-2026-74417-ee3c@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@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.
The Linux kernel CVE team has assigned CVE-2026-74417 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.39 with commit ff72145badb834e8051719ea66e024784d000cb4 and fixed in 6.6.145 with commit b7b44937c548c2c987fcdd129f8896741004bed6
Issue introduced in 2.6.39 with commit ff72145badb834e8051719ea66e024784d000cb4 and fixed in 6.12.97 with commit 415bb9893e249e46aa5159f7363a11512cf06fa9
Issue introduced in 2.6.39 with commit ff72145badb834e8051719ea66e024784d000cb4 and fixed in 6.18.40 with commit d9dfa176899d488e48bb7342d2c43ddd36e66318
Issue introduced in 2.6.39 with commit ff72145badb834e8051719ea66e024784d000cb4 and fixed in 7.1.5 with commit dfc7b5b5599472277e71e5bd2712740651c7c5be
Issue introduced in 2.6.39 with commit ff72145badb834e8051719ea66e024784d000cb4 and fixed in 7.2-rc1 with commit ce3b24eb3ee8f82de851535f516bf21f83e82259
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2026-74417
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/gpu/drm/radeon/radeon_gem.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/b7b44937c548c2c987fcdd129f8896741004bed6
https://git.kernel.org/stable/c/415bb9893e249e46aa5159f7363a11512cf06fa9
https://git.kernel.org/stable/c/d9dfa176899d488e48bb7342d2c43ddd36e66318
https://git.kernel.org/stable/c/dfc7b5b5599472277e71e5bd2712740651c7c5be
https://git.kernel.org/stable/c/ce3b24eb3ee8f82de851535f516bf21f83e82259
reply other threads:[~2026-08-15 6:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026081512-CVE-2026-74417-ee3c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox