From: Liam Merwick <liam.merwick@oracle.com>
To: stable@vger.kernel.org
Cc: vasant.hegde@amd.com, joerg.roedel@amd.com,
iommu@lists.linux.dev, dheerajkumar.srivastava@amd.com,
bp@alien8.de, Michael.Roth@amd.com, sashal@kernel.org,
linux-coco@lists.linux.dev, liam.merwick@oracle.com
Subject: [PATCH linux-6.12.y v1 0/2] Backporting SEV-SNP CVE-2023-20585 to linux-stable
Date: Fri, 17 Jul 2026 10:49:07 +0000 [thread overview]
Message-ID: <20260717104909.3850331-1-liam.merwick@oracle.com> (raw)
Two commits from Linux 7.1-rc3 fix CVE-2023-20585 which affects SEV-SNP.
"Insufficient checks of the RMP on host buffer access in IOMMU may allow an
attacker with privileges and a compromised hypervisor to trigger an out of
bounds condition without RMP checks, resulting in a potential loss of
confidential guest integrity." [1]
These are suitable candidates for stable branches but stable@vger.kernel.org
wasn't CC'ed at the time.
1f44aab79bac ("iommu/amd: Use maximum PPR log buffer size when SNP is enabled on Family 0x19") [v7.1-rc3~24^2~2]
58c0ac6125d8 ("iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19") [v7.1-rc3~24^2~3]
The upstream commits apply cleanly to linux-7.0.y and linux-6.18.y
and an AUTOSEL email[2] was sent (but not pulled so far).
[ The AI analysis in the AUTOSEL patch said that the patches didn't apply
cleanly to linux-6.18.y but that is not my experience. ]
There are conflicts applying them to linux-6.12.y due to the lack of upstream
AMD IOMMU kdump buffer reuse code, introduced to v6.18 by commit
f32fe7cb0198 ("iommu/amd: Add support to remap/unmap IOMMU buffers for kdump")
so I have included patches here which address those.
Tested on AMD machines with Zen4 (impacted) and Zen5 (not impacted) CPUs.
[1] https://www.amd.com/en/resources/product-security/bulletin/amd-sb-3016.html
[2] https://lore.kernel.org/all/20260520111944.3424570-59-sashal@kernel.org
Vasant Hegde (2):
iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19
iommu/amd: Use maximum PPR log buffer size when SNP is enabled on Family 0x19
drivers/iommu/amd/amd_iommu.h | 3 +
drivers/iommu/amd/amd_iommu_types.h | 21 ++++---
drivers/iommu/amd/init.c | 90 ++++++++++++++++++++++-------
drivers/iommu/amd/iommu.c | 2 +-
drivers/iommu/amd/ppr.c | 10 ++--
5 files changed, 92 insertions(+), 34 deletions(-)
--
2.52.0
next reply other threads:[~2026-07-17 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 10:49 Liam Merwick [this message]
2026-07-17 10:49 ` [PATCH linux-6.12.y v1 1/2] iommu/amd: Use maximum Event log buffer size when SNP is enabled on Family 0x19 Liam Merwick
2026-07-17 10:49 ` [PATCH linux-6.12.y v1 2/2] iommu/amd: Use maximum PPR " Liam Merwick
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=20260717104909.3850331-1-liam.merwick@oracle.com \
--to=liam.merwick@oracle.com \
--cc=Michael.Roth@amd.com \
--cc=bp@alien8.de \
--cc=dheerajkumar.srivastava@amd.com \
--cc=iommu@lists.linux.dev \
--cc=joerg.roedel@amd.com \
--cc=linux-coco@lists.linux.dev \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vasant.hegde@amd.com \
/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