CVE-2024-56761
Last modified
CVE-2024-56761 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.22% chance of exploitation in the next 30 days.
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 ]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6, < 6.12.8 | — |
| Linux | Linux Kernel | 6.13 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-56761?
How severe is CVE-2024-56761?
How do I fix CVE-2024-56761?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-56756In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56757In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56758In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56759In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-5676The Paradox IP150 Internet Module in version 1.40.00 is vuln…6.8
- CVE-2024-56760In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56762Rejected reason: This CVE ID has been rejected or withdrawn …
- CVE-2024-56763In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2024-56764In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-56765In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-56766In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2024-56767In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2024-56761?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
