CVE-2024-56761 Details
Description
In the Linux kernel, the following vulnerability has been resolved: x86/fred: Clear WFE in missing-ENDBRANCH #CPs An indirect branch instruction sets the CPU indirect branch tracker (IBT) into WAIT_FOR_ENDBRANCH (WFE) state and WFE stays asserted across the instruction boundary. When the decoder finds an inappropriate instruction while WFE is set ENDBR, the CPU raises a #CP fault. For the "kernel IBT no ENDBR" selftest where #CPs are deliberately triggered, the WFE state of the interrupted context needs to be cleared to let execution continue. Otherwise when the CPU resumes from the instruction that just caused the previous #CP, another missing-ENDBRANCH #CP is raised and the CPU enters a dead loop. This is not a problem with IDT because it doesn't preserve WFE and IRET doesn't set WFE. But FRED provides space on the entry stack (in an expanded CS area) to save and restore the WFE state, thus the WFE state is no longer clobbered, so software must clear it. Clear WFE to avoid dead looping in ibt_clear_fred_wfe() and the !ibt_fatal code path when execution is allowed to continue. Clobbering WFE in any other circumstance is a security-relevant bug. [ dhansen: changelog rewording ]
A vulnerability in the Linux kernel's handling of the indirect branch tracker (IBT) can lead to a deadlock situation. This issue arises when an indirect branch instruction sets the CPU's IBT into a WAIT_FOR_ENDBRANCH (WFE) state, which is then improperly maintained across instruction boundaries. During the 'kernel IBT no ENDBR' self-test, where #CP faults are intentionally triggered, the WFE state must be cleared to prevent execution from getting stuck in a loop. While the Interrupt Descriptor Table (IDT) does not retain the WFE state, the FRED mechanism does, requiring software to manually clear it. Failure to do so can cause the CPU to repeatedly enter a dead loop, exacerbating the problem.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/151447859d6fb0dcce8259f0971c6e94fb801661 | kernel.org | |
| https://git.kernel.org/stable/c/b939f108e86b76119428a6fa4e92491e09ac7867 | kernel.org | Patch |
| https://git.kernel.org/stable/c/dc81e556f2a017d681251ace21bf06c126d5a192 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.6, < 6.12.8 6.13 rc1 6.13 rc2 6.13 rc3 6.13 rc4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 9, 2025 | CVE Modified | kernel.org |
| Jan 7, 2025 | Initial Analysis | [email protected] |
| Jan 6, 2025 | New CVE Received | kernel.org |