mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kenta Akagi <k@mgml.me>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	stable@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Kenta Akagi <k@mgml.me>
Subject: [PATCH 5.15.y v3 0/7] KVM: fixes for CVE-2026-46113 and related issues
Date: Mon, 14 Sep 2026 00:55:16 +0900	[thread overview]
Message-ID: <20260913155523.7423-1-k@mgml.me> (raw)

This is a backport of the CVE-2026-46113 and CVE-2026-53359 fixes to 5.15.y.

The only difference from Paolo's v2 [1] is that commit ef057cbf825e ("KVM:
x86/mmu: Ensure hugepage is in by slot before checking max mapping level") is
not included, as it has already been backported to 5.15.y.

I believe v2 was not merged two months ago because of the regression reported
in [2], which occurs when only these patches are applied.

Commit a955cad84cda ("KVM: x86/mmu: Retry page fault if root is invalidated by
memslot update") was proposed as a fix for this regression. I have confirmed
that applying the v2 patches triggers the WARN, and that applying a955cad84cda
fixes it.

Since a955cad84cda has already been backported to 5.15.218, it is not included
in this series.

[1] https://lore.kernel.org/all/20260626174620.1819772-1-pbonzini@redhat.com/
[2] https://lore.kernel.org/kvm/20260630223723.83727-1-zcgao@amazon.com/ 

David Matlack (2):
  KVM: x86/mmu: Use a bool for direct
  KVM: x86/mmu: Stop passing "direct" to mmu_alloc_root()

Paolo Bonzini (4):
  KVM: x86/mmu: Derive shadow MMU page role from parent
  KVM: x86/mmu: Always pass 0 for @quadrant when gptes are 8 bytes
  KVM: x86/mmu: pull call to drop_large_spte() into __link_shadow_page()
  KVM: x86: Fix shadow paging use-after-free due to unexpected role

Sean Christopherson (1):
  KVM: x86: Fix shadow paging use-after-free due to unexpected GFN

 arch/x86/kvm/mmu/mmu.c         | 174 +++++++++++++++++++++------------
 arch/x86/kvm/mmu/paging_tmpl.h |  32 +++---
 arch/x86/kvm/mmu/spte.h        |   5 +
 3 files changed, 129 insertions(+), 82 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-09-13 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-13 15:55 Kenta Akagi [this message]
2026-09-13 15:55 ` [PATCH 5.15.y v3 1/7] KVM: x86/mmu: Use a bool for direct Kenta Akagi
2026-09-13 15:55 ` [PATCH 5.15.y v3 2/7] KVM: x86/mmu: Stop passing "direct" to mmu_alloc_root() Kenta Akagi
2026-09-13 15:55 ` [PATCH 5.15.y v3 3/7] KVM: x86/mmu: Derive shadow MMU page role from parent Kenta Akagi
2026-09-15  2:03   ` Sasha Levin
2026-09-13 15:55 ` [PATCH 5.15.y v3 4/7] KVM: x86/mmu: Always pass 0 for @quadrant when gptes are 8 bytes Kenta Akagi
2026-09-15  2:03   ` Sasha Levin
2026-09-13 15:55 ` [PATCH 5.15.y v3 5/7] KVM: x86/mmu: pull call to drop_large_spte() into __link_shadow_page() Kenta Akagi
2026-09-13 15:55 ` [PATCH 5.15.y v3 6/7] KVM: x86: Fix shadow paging use-after-free due to unexpected GFN Kenta Akagi
2026-09-13 15:55 ` [PATCH 5.15.y v3 7/7] KVM: x86: Fix shadow paging use-after-free due to unexpected role Kenta Akagi

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=20260913155523.7423-1-k@mgml.me \
    --to=k@mgml.me \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®