CVE-2024-56761: x86/fred: Clear WFE in missing-ENDBRANCH #CPs

Published Jan 6, 2025
·
Updated

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 WAITFORENDBRANCH (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 ibtclearfredwfe() and the !ibtfatal code path when execution is allowed to continue.

Clobbering WFE in any other circumstance is a security-relevant bug.

[ dhansen: changelog rewording ]

Other sources

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

6 affected componentsFixes available
Linux Linux kernel>=6.6<6.12.8
Linux Linux kernel=6.13-rc1
Linux Linux kernel=6.13-rc2
Linux Linux kernel=6.13-rc3
Linux Linux kernel=6.13-rc4
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.22-16.12.25-1

Event History

Jan 6, 2025
CVE Published
via MITRE·04:20 PM
Data Sourced
via MITRE·04:20 PM
Description
Mar 27, 2025
Data Sourced
via Launchpad·06:47 PM
Description
Apr 28, 2025
Data Sourced
via Ubuntu·06:54 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·06:55 PM
DescriptionAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-56761?

CVE-2024-56761 has not been publicly assigned a CVSS score, but it is related to a critical functionality in the Linux kernel.

2

How do I fix CVE-2024-56761?

To fix CVE-2024-56761, you should upgrade to a patched version of the Linux kernel that addresses this vulnerability.

3

Which versions of the Linux kernel are affected by CVE-2024-56761?

CVE-2024-56761 affects Linux kernel versions between 6.6 and 6.12.8, as well as versions 6.13-rc1 to 6.13-rc4.

4

What type of vulnerability is CVE-2024-56761?

CVE-2024-56761 is an indirect branch tracking vulnerability that impacts the x86 architecture in the Linux kernel.

5

Is there a workaround for CVE-2024-56761?

Currently, the recommended approach for CVE-2024-56761 is to apply the latest patches rather than relying on workarounds.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203