All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-99629: drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for navi10_ih
Date: Fri, 20 Nov 2026 06:50:15 +0100	[thread overview]
Message-ID: <2026112036-CVE-2026-99629-e500@gregkh> (raw)

From: Greg Kroah-Hartman <gregkh@kernel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts for navi10_ih

Port this change to navi10_ih.c:
commit afbf7955ff01 ("drm/amdgpu: clear RB_OVERFLOW bit when enabling interrupts")

Setting IH_RB_WPTR to 0 does not clear RB_OVERFLOW if RB_ENABLE is not
set. Pulse WPTR_OVERFLOW_CLEAR after RB_ENABLE (and with
WPTR_OVERFLOW_ENABLE) so overflow is cleared when interrupts are
enabled.

(cherry picked from commit 713fb4ab04f4d2af6120f8eb607c5673b2759b38)

The Linux kernel CVE team has assigned CVE-2026-99629 to this issue.


Affected and fixed versions
===========================

	Fixed in 6.12.118 with commit 53f0c61efb5ff1f203659f3ebb8ccacc39ae28bd
	Fixed in 6.18.64 with commit 00ae61183bff39238018de3db81d835d87618b42
	Fixed in 7.3.5 with commit d7a7d21bebae5e2bf6f0b89d3dd6828de46c8614
	Fixed in 7.4-rc2 with commit 146b96974b33b8cca52755ffed3cd24a82836013

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-99629
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/navi10_ih.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/53f0c61efb5ff1f203659f3ebb8ccacc39ae28bd
	https://git.kernel.org/stable/c/00ae61183bff39238018de3db81d835d87618b42
	https://git.kernel.org/stable/c/d7a7d21bebae5e2bf6f0b89d3dd6828de46c8614
	https://git.kernel.org/stable/c/146b96974b33b8cca52755ffed3cd24a82836013

                 reply	other threads:[~2026-11-20  5:55 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=2026112036-CVE-2026-99629-e500@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.