From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5159715820E for ; Fri, 3 May 2024 17:46:48 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714758408; cv=none; b=kT/lsy0+JpSFODIiGmg+xD+tJzimQjnv0Arnr9y1lb2fcsTsxHZaXZomciOH0r6kMe90BysOG8L/Hmd3GgSy8vN+ij0aSS1jd8xysXIEQdVjxSb+p43/Z7OnWQ1yliOE16XTU7bh6536AtbsIdKgDhgPW5abPF/G5W1mEdkqhE4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1714758408; c=relaxed/simple; bh=JqfnKlX+QCzPQcPkZsJuVq+QSYfrrHtt2TgRBugvtsA=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=V2/YeWHNFY6f1fTZzSKzyz6RI/UaBuKERahGaXYwDjshL7lWLuWemiUKLNSQXqH/VAIfRiQUuuzpdCjv0udwDykHNl/axrYfyAOGpvO+6JgsluoWDjfzdPmwnTE8ikeYGYoL3QVueVwWeCgvnaVN1QWrHYNOe4rwSHlC5PJFbi4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=o05eRRIu; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="o05eRRIu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id BD9E3C116B1; Fri, 3 May 2024 17:46:47 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1714758408; bh=JqfnKlX+QCzPQcPkZsJuVq+QSYfrrHtt2TgRBugvtsA=; h=From:To:Cc:Subject:Date:Reply-to:From; b=o05eRRIuETAxqGKrqVhLVZQrxi+kc4lbijSzp6UD8Yzp0IScX7NtZ/QKeVakfvUrW /0PrBNcAYGQHoQk1JZ16Tshy0/asRID+tZ4Z6AeDZnfa1BOvE8bd0aI6uaerwHcv6a jmx1WLee8ccl7vxlC94bkXuGPoBhCR1hW8O2GTqA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2022-48704: drm/radeon: add a force flush to delay work when radeon Date: Fri, 3 May 2024 19:46:00 +0200 Message-ID: <2024050351-CVE-2022-48704-e1ea@gregkh> X-Mailer: git-send-email 2.45.0 Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Reply-to: , X-Developer-Signature: v=1; a=openpgp-sha256; l=4547; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=JqfnKlX+QCzPQcPkZsJuVq+QSYfrrHtt2TgRBugvtsA=; b=owGbwMvMwCRo6H6F97bub03G02pJDGmmSucP7245J7F99x4Jrs/n9j61q5mVwWlapu827+fWQ /UrK6cWdcSyMAgyMciKKbJ82cZzdH/FIUUvQ9vTMHNYmUCGMHBxCsBEwtMZFpx1PffmxPyDGyey nPF4pq/1+1D4HHmGear61TeXcu5ZEb3oR7THCwcD/g/m7QA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit Description =========== In the Linux kernel, the following vulnerability has been resolved: drm/radeon: add a force flush to delay work when radeon Although radeon card fence and wait for gpu to finish processing current batch rings, there is still a corner case that radeon lockup work queue may not be fully flushed, and meanwhile the radeon_suspend_kms() function has called pci_set_power_state() to put device in D3hot state. Per PCI spec rev 4.0 on 5.3.1.4.1 D3hot State. > Configuration and Message requests are the only TLPs accepted by a Function in > the D3hot state. All other received Requests must be handled as Unsupported Requests, > and all received Completions may optionally be handled as Unexpected Completions. This issue will happen in following logs: Unable to handle kernel paging request at virtual address 00008800e0008010 CPU 0 kworker/0:3(131): Oops 0 pc = [] ra = [] ps = 0000 Tainted: G W pc is at si_gpu_check_soft_reset+0x3c/0x240 ra is at si_dma_is_lockup+0x34/0xd0 v0 = 0000000000000000 t0 = fff08800e0008010 t1 = 0000000000010000 t2 = 0000000000008010 t3 = fff00007e3c00000 t4 = fff00007e3c00258 t5 = 000000000000ffff t6 = 0000000000000001 t7 = fff00007ef078000 s0 = fff00007e3c016e8 s1 = fff00007e3c00000 s2 = fff00007e3c00018 s3 = fff00007e3c00000 s4 = fff00007fff59d80 s5 = 0000000000000000 s6 = fff00007ef07bd98 a0 = fff00007e3c00000 a1 = fff00007e3c016e8 a2 = 0000000000000008 a3 = 0000000000000001 a4 = 8f5c28f5c28f5c29 a5 = ffffffff810f4338 t8 = 0000000000000275 t9 = ffffffff809b66f8 t10 = ff6769c5d964b800 t11= 000000000000b886 pv = ffffffff811bea20 at = 0000000000000000 gp = ffffffff81d89690 sp = 00000000aa814126 Disabling lock debugging due to kernel taint Trace: [] si_dma_is_lockup+0x34/0xd0 [] radeon_fence_check_lockup+0xd0/0x290 [] process_one_work+0x280/0x550 [] worker_thread+0x70/0x7c0 [] worker_thread+0x130/0x7c0 [] kthread+0x200/0x210 [] worker_thread+0x0/0x7c0 [] kthread+0x14c/0x210 [] ret_from_kernel_thread+0x18/0x20 [] kthread+0x0/0x210 Code: ad3e0008 43f0074a ad7e0018 ad9e0020 8c3001e8 40230101 <88210000> 4821ed21 So force lockup work queue flush to fix this problem. The Linux kernel CVE team has assigned CVE-2022-48704 to this issue. Affected and fixed versions =========================== Fixed in 4.9.328 with commit b878da58df2c Fixed in 4.14.293 with commit 4e25e8f27fdb Fixed in 4.19.258 with commit c0a45f41fde4 Fixed in 5.4.213 with commit c72d97146fc5 Fixed in 5.10.143 with commit 826b46fd5974 Fixed in 5.15.68 with commit 5a7a5b2edac4 Fixed in 5.19.9 with commit 16cb367daa44 Fixed in 6.0 with commit f461950fdc37 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-2022-48704 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_device.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/b878da58df2c40b08914d3960e2224040fd1fbfe https://git.kernel.org/stable/c/4e25e8f27fdbdc6fd55cc572a9939bf24500b9e8 https://git.kernel.org/stable/c/c0a45f41fde4a0f2c900f719817493ee5c4a5aa3 https://git.kernel.org/stable/c/c72d97146fc5a4dff381b1737f6167e89860430d https://git.kernel.org/stable/c/826b46fd5974113515abe9e4fc8178009a8ce18c https://git.kernel.org/stable/c/5a7a5b2edac4b05abd744eeaebda46d9dacd952d https://git.kernel.org/stable/c/16cb367daa446923d82e332537f446a4cc784b40 https://git.kernel.org/stable/c/f461950fdc374a3ada5a63c669d997de4600dffe