Re: [PATCH v10 00/26] Control-flow Enforcement: Shadow Stack
From: Sean Christopherson <hidden>
Date: 2020-07-23 16:25:39
Also in:
linux-arch, linux-doc, linux-mm, lkml
From: Sean Christopherson <hidden>
Date: 2020-07-23 16:25:39
Also in:
linux-arch, linux-doc, linux-mm, lkml
On Wed, Apr 29, 2020 at 03:07:06PM -0700, Yu-cheng Yu wrote:
Control-flow Enforcement (CET) is a new Intel processor feature that blocks return/jump-oriented programming attacks. Details can be found in "Intel 64 and IA-32 Architectures Software Developer's Manual" [1]. This series depends on the XSAVES supervisor state series that was split out and submitted earlier [2].
...
Yu-cheng Yu (25):
x86/cpufeatures: Add CET CPU feature flags for Control-flow
Enforcement Technology (CET)
x86/fpu/xstate: Introduce CET MSR XSAVES supervisor statesHow would people feel about taking the above two patches (02 and 03 in the series) through the KVM tree to enable KVM virtualization of CET before the kernel itself gains CET support? I.e. add the MSR and feature bits, along with the XSAVES context switching. The feature definitons could use "" to suppress displaying them in /proc/cpuinfo to avoid falsely advertising CET to userspace. AIUI, there are ABI issues that need to be sorted out, and that is likely going to drag on for some time. Is this a "hell no" sort of idea, or something that would be feasible if we can show that there are no negative impacts to the kernel?