CVE-2026-31561x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By Linux
- 46 days later
· 46 days later
Published
- 17 days later
· 17 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (19 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected ff45746fbf005f96e42bea466698e3fdbf926013 – < d7853d9fe94abf43b46c57b0b7f8418198b7615a
- affected ff45746fbf005f96e42bea466698e3fdbf926013 – < a6e14114684d2324e5401617d6d01acb4a4e0e22
- affected ff45746fbf005f96e42bea466698e3fdbf926013 – < 00d956dafa76f86a73424fe5cce3d604a8be2e4b
- affected ff45746fbf005f96e42bea466698e3fdbf926013 – < 411df123c017169922cc767affce76282b8e6c85
- affected 6.9
- unaffected < 6.9
- unaffected 6.12.80 – ≤ 6.12.*
- unaffected 6.18.21 – ≤ 6.18.*
- unaffected 6.19.11 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References4
- https://git.kernel.org/stable/c/d7853d9fe94abf43b46c57b0b7f8418198b7615a (opens in a new tab)
- https://git.kernel.org/stable/c/a6e14114684d2324e5401617d6d01acb4a4e0e22 (opens in a new tab)
- https://git.kernel.org/stable/c/00d956dafa76f86a73424fe5cce3d604a8be2e4b (opens in a new tab)
- https://git.kernel.org/stable/c/411df123c017169922cc767affce76282b8e6c85 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-25454 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-31561)Record last updated .