From: "Adam Dunlap via groups.io" <acdunlap=google.com@groups.io>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: devel@edk2.groups.io, Borislav Petkov <bp@alien8.de>,
Peter Gonda <pgonda@google.com>
Subject: Re: [edk2-devel] [PATCH] OvmfPkg: Harden #VC instruction emulation somewhat (CVE-2024-25742)
Date: Fri, 19 Apr 2024 10:39:35 -0700 [thread overview]
Message-ID: <CAMBK9=aVOH8Tot1g3peWk0H2iDd=u4eV82sYTunD_f2DM-mqGw@mail.gmail.com> (raw)
In-Reply-To: <d2290ad6-8001-b088-fcf7-0b1609ee5ea9@amd.com>
On Fri, Apr 19, 2024 at 8:13 AM Tom Lendacky <thomas.lendacky@amd.com> wrote:
>
> On 4/17/24 11:54, Adam Dunlap wrote:
> > +
> > + case SVM_EXIT_INVD:
> > + break;
>
> This changes the current behavior today, but I'm ok with that.
>
Whoops, I should've checked that. Should we delete InvdExit() then, if
it's dead code?
> > +
> > + case SVM_EXIT_MONITOR:
> > + CcDecodeModRm (Regs, InstructionData);
> > +
> > + if ((OpCode == 0x01) && (InstructionData->ModRm.Uint8 == 0xc8)) {
>
> This should also handle the MONITORX opcode (hmmm... I need to send a
> patch to the kernel).
>
> > + return 0;
> > + }
> > +
> > + break;
> > +
> > + case SVM_EXIT_MWAIT:
> > + CcDecodeModRm (Regs, InstructionData);
> > +
> > + if ((OpCode == 0x01) && (InstructionData->ModRm.Uint8 == 0xc9)) {
>
> Same here for MWAITX.
>
> Thanks,
> Tom
Got it! I'll send out a new patch shortly if I can figure out how to
use git send-email correctly.
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118037): https://edk2.groups.io/g/devel/message/118037
Mute This Topic: https://groups.io/mt/105581633/7686176
Mute #vc:https://edk2.groups.io/g/devel/mutehashtag/vc
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-04-19 17:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 16:54 [edk2-devel] [PATCH] OvmfPkg: Harden #VC instruction emulation somewhat (CVE-2024-25742) Adam Dunlap via groups.io
2024-04-17 17:08 ` Ard Biesheuvel
2024-04-17 17:45 ` Adam Dunlap via groups.io
2024-04-18 8:03 ` Yao, Jiewen
2024-04-18 12:15 ` Gerd Hoffmann
2024-04-18 15:39 ` Adam Dunlap via groups.io
2024-04-18 15:43 ` Peter Gonda via groups.io
2024-04-19 11:31 ` Gerd Hoffmann
2024-04-19 14:56 ` Lendacky, Thomas via groups.io
2024-04-19 15:12 ` Lendacky, Thomas via groups.io
2024-04-19 17:39 ` Adam Dunlap via groups.io [this message]
2024-04-19 18:21 ` [edk2-devel] [PATCH v2] " Adam Dunlap via groups.io
2024-04-22 14:12 ` Lendacky, Thomas via groups.io
2024-04-23 9:27 ` Gerd Hoffmann
2024-04-24 16:27 ` Ard Biesheuvel
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-list 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='CAMBK9=aVOH8Tot1g3peWk0H2iDd=u4eV82sYTunD_f2DM-mqGw@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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