From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-68249: drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON()
Date: Mon, 10 Aug 2026 13:59:26 +0200 [thread overview]
Message-ID: <2026081020-CVE-2026-68249-6a72@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/sdma5.0: replace BUG_ON() with WARN_ON()
There's no need to crash the kernel for these cases.
(cherry picked from commit 8d144a0eb09537055841af48c9e7c2d4cd48e84d)
The Linux kernel CVE team has assigned CVE-2026-68249 to this issue.
Affected and fixed versions
===========================
Fixed in 6.6.148 with commit f6212bc1bbd936fd9f7d77168b0c8b0019477b64
Fixed in 6.12.101 with commit 28337e5d7df429bac7de64b17f1a595147778caa
Fixed in 6.18.42 with commit d20b5c139b2906bcd8ab4bfe5b8be500318161d1
Fixed in 7.1.6 with commit 0027cb19b0449ad6babedb1af285a713ab05c97f
Fixed in 7.2-rc2 with commit 9e98ed3113943257ad6e5c1e6beddbdb482a70ad
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-68249
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/amd/amdgpu/sdma_v5_0.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/f6212bc1bbd936fd9f7d77168b0c8b0019477b64
https://git.kernel.org/stable/c/28337e5d7df429bac7de64b17f1a595147778caa
https://git.kernel.org/stable/c/d20b5c139b2906bcd8ab4bfe5b8be500318161d1
https://git.kernel.org/stable/c/0027cb19b0449ad6babedb1af285a713ab05c97f
https://git.kernel.org/stable/c/9e98ed3113943257ad6e5c1e6beddbdb482a70ad
reply other threads:[~2026-08-10 12:07 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=2026081020-CVE-2026-68249-6a72@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.