Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2026-31561— x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask

EPSS 0.01% · P2
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2026-31561

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
x86/cpu: Remove X86_CR4_FRED from the CR4 pinned bits mask
Source: NVD (National Vulnerability Database)
Vulnerability 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.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于FRED CR4位被加入CR4固定位掩码,导致在AP初始化期间异常无法处理,可能引发三重故障。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux ff45746fbf005f96e42bea466698e3fdbf926013 ~ d7853d9fe94abf43b46c57b0b7f8418198b7615a -
LinuxLinux 6.9 -

II. Public POCs for CVE-2026-31561

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-31561

登录查看更多情报信息。

Same Patch Batch · Linux · 2026-04-24 · 138 CVEs total

CVE-2026-316099.8 CRITICALsmb: client: avoid double-free in smbd_free_send_io() after smbd_send_batch_flush()
CVE-2026-316089.8 CRITICALsmb: server: avoid double-free in smb_direct_free_sendmsg after smb_direct_flush_send_list
CVE-2026-316579.8 CRITICALbatman-adv: hold claim backbone gateways by reference
CVE-2026-316339.8 CRITICALrxrpc: Fix integer overflow in rxgk_verify_response()
CVE-2026-316079.8 CRITICALusbip: validate number_of_packets in usbip_pack_ret_submit()
CVE-2026-316699.8 CRITICALmptcp: fix slab-use-after-free in __inet_lookup_established
CVE-2026-316689.8 CRITICALseg6: separate dst_cache for input and output paths in seg6 lwtunnel
CVE-2026-316599.8 CRITICALbatman-adv: reject oversized global TT response buffers
CVE-2026-315899.8 CRITICALmm: call ->free_folio() directly in folio_unmap_invalidate()
CVE-2026-315369.8 CRITICALsmb: server: let send_done handle a completion without IB_SEND_SIGNALED
CVE-2026-316379.8 CRITICALrxrpc: reject undecryptable rxkad response tickets
CVE-2026-316499.8 CRITICALnet: stmmac: fix integer underflow in chain mode
CVE-2026-316369.1 CRITICALrxrpc: fix RESPONSE authenticator parser OOB read
CVE-2026-315538.8 HIGHKVM: arm64: Fix the descriptor address in __kvm_at_swap_desc()
CVE-2026-316298.8 HIGHnfc: llcp: add missing return after LLCP_CLOSED checks
CVE-2026-315888.8 HIGHKVM: x86: Use scratch field in MMIO fragment to hold small write values
CVE-2026-315708.8 HIGHcan: gw: fix OOB heap access in cgw_csum_crc8_rel()
CVE-2026-315588.8 HIGHLoongArch: KVM: Make kvm_get_vcpu_by_cpuid() more robust
CVE-2026-316228.8 HIGHNFC: digital: Bounds check NFC-A cascade depth in SDD response handler
CVE-2026-316118.6 HIGHksmbd: require 3 sub-authorities before reading sub_auth[2]

Showing top 20 of 138 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2026-31561

No comments yet


Leave a comment