From mboxrd@z Thu Jan 1 00:00:00 1970 Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.remote-ip=100.103.45.18 ARC-Seal: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; cv=none; t=1795154113; b=PB/oPhc5CNXOG3V1v3aeR4KjGRjPL+XmXHyxh0Sf8ri+Qjo+pHgRmmXLE+BkwqwJmYz2 W6OLVnaC6ld7XqNCjDBPENqrHNcKX1CAaogtjQNDfRZdhgAIzc2iAVJHU1uTprpo4WE5H ydIegW+Shi0VVvZduR6UHZRB5LdSSNXU53/npBdFRFPMoA/ew+Y1hYGwfN76SPNGvMViC LNCxKMscuAB7RD4I0JKxeuAYF9rFnunEkYiaxqI2wB8fbka0ZR2rWXwPHE/kXOPQqpHgH VqSXDU6+0eQ4ZbJnhTq7QB0BduTyplELnxNOI/WTbYi6jYWD558FthjlWDzF/9V2xnA== ARC-Message-Signature: i=1; d=subspace.kernel.org; s=arc20261015; a=rsa-sha256; c=relaxed/relaxed; t=1795154113; h=Received:DKIM-Signature:From:To:Cc:Subject:Date:Message-ID:X-Mailer: Reply-To:MIME-Version:Lines:X-Developer-Signature:X-Developer-Key: Content-Transfer-Encoding; bh=YutvlgcX3iGWqAH4uM+ZqiZyAB2TjwfbHtw0ibYX4Is=; b=Qzkw7Zr+PdZa6UqmETm4LGSDMYk1lod6pHpZ6x9t2aKyNGQNa/Z2bf3e7bIjiYyqKyum ixeRPPRO+/jr2ctri24NsZ/2jKZCKUV1/bO9XafZK9bSP46otkVkhwmwAg1s4/+pb2t2N M9cmpAxQjwu/zWqJ+NKNlFJN3riUBw4HFZzaTgDluJomAqgyW72nEIuT61IfXoZm1SKUX RU57x/3iinu8SU85JF4PRhvfyYlolR9oKh/J9tex2AhP3hdCFBFm5kc8INa3aFNPOdEgG Edw8dCPiUe3eLudzt6n8zADFisyAQPRoE6hrSBVaVryzPt3AWJyjR9ulHcyW5RQ8JOA== ARC-Authentication-Results: i=1; smtp.subspace.kernel.org; dkim=pass header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=o24fxt+E; arc=none smtp.remote-ip=100.103.45.18 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id D4462606A325 for ; Fri, 20 Nov 2026 05:55:13 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.a=rsa-sha256 header.s=korg header.b=o24fxt+E Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2B5FF1F000CA; Fri, 20 Nov 2026 05:55:13 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1795154113; bh=YutvlgcX3iGWqAH4uM+ZqiZyAB2TjwfbHtw0ibYX4Is=; h=From:To:Cc:Subject:Date:Reply-To; b=o24fxt+EVOMg6DOIJTRAMgXd+bdMPP252LRn+rElikvcZpBqfyDh8B8WlE8f1PmPK SrSwjt19inWLCuyqTTx4RyjsR2s7U9nuekzxNfoJuCG9RQlqfJFGXYtgMIvFEAjosQ 5Ij9eYnTOufH6FhV9geY+8gmxhlEqr+rxzrjlbRc= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman 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 Message-ID: <2026112036-CVE-2026-99629-e500@gregkh> X-Mailer: git-send-email 2.56.1 Reply-To: , X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Post: List-Help: List-Subscribe: List-Unsubscribe: List-Owner: Precedence: list MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2323; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=km12sBcvpAeiS3jHbPMlWzWbJPj3IDXtl+j6lzGtiFk=; b=owGbwMvMwCRo6H6F97bub03G02pJDFn/7xc4cC7c8a/fWufb3uIXxsG1z2tk3yz2+f+n+VTWl KY9Z7h8O2JZGASZGGTFFFm+bOM5ur/ikKKXoe1pmDmsTCBDGLg4BWAi/gIMc/iX9ZzyipV+UWhf I2x2oTojcpukHsP8Qls3R4YvH6MSfkr4uuvIf9l1JfEkAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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