x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask
Commit in Fixes added the FRED CR4 bit to the CR4 pinned bits mask so that whenever something else modifies CR4, that bit remains set. Which in itself is a perfectly fine idea.
However, there's an issue when during boot FRED is initialized: first on the BSP and later on the APs. Thus, there's a window in time when exceptions cannot be handled.
This becomes particularly nasty when running as SEV-{ES,SNP} or TDX guests which, when they manage to trigger exceptions during that short window described above, triple fault due to FRED MSRs not being set up yet.
See Link tag below for a much more detailed explanation of the situation.
So, as a result, the commit in that Link URL tried to address this shortcoming by temporarily disabling CR4 pinning when an AP is not online yet.
However, that is a problem in itself because in this case, an attack on the kernel needs to only modify the online bit - a single bit in RW memory - and then disable CR4 pinning and then disable SM*P, leading to more and worse things to happen to the system.
From the CVE record · Linux
The Linux kernel's x86 CR4 handling can temporarily disable CR4 pinning while an application processor is not online. An attacker who can modify a kernel online bit in writable memory could exploit this condition to disable CR4 pinning and SM*P. The input does not specify whether this requires local access or authentication.
Engineers running Linux kernels with the affected x86 CR4 pinning behavior should check their systems; affected versions are not specified.