CVE-2024-35996cpu: Re-enable CPU mitigations by default for !X86 architectures
Updated under an hour ago ()
Does this affect you?
It affects Linux and 6 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
In the Linux kernel, the following vulnerability has been resolved: cpu: Re-enable CPU mitigations by default for !X86 architectures Rename x86's to CPU_MITIGATIONS, define it in generic code, and force it on for all architectures exception x86. A recent commit to turn mitigations off by default if SPECULATION_MITIGATIONS=n kinda sorta missed that "cpu_mitigations" is completely generic, whereas SPECULATION_MITIGATIONS is x86-specific. Rename x86's SPECULATIVE_MITIGATIONS instead of keeping both and have it select CPU_MITIGATIONS, as having two configs for the same thing is unnecessary and confusing. This will also allow x86 to use the knob to manage mitigations that aren't strictly related to speculative execution. Use another Kconfig to communicate to common code that CPU_MITIGATIONS is already defined instead of having x86's menu depend on the common CPU_MITIGATIONS. This allows keeping a single point of contact for all of x86's mitigations, and it's not clear that other architectures *want* to allow disabling mitigations at compile-time.
- CVSS
- 5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Linux
- NVD analysis
- Modified
- Record last updated
- Oct 15, 2026
- First seen by InfoSec Signals
- Oct 15, 2026
Affected products
Linux Linux linux:linux (from the name) | from 30da4180fd768973189dc364648f9c436e57b01d before af6d6a923b40bf6471e44067ac61cc5814b48e7f; 70688450dddaf91e12fd4fc625da3297025932c9 builds before 36b32816fbab267611f073223f1b0b816ec5920f; from 9c09773917fbb77dff85b433e1e89123fc5fb530 before 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9; from 2978ee7c973ce81b6e51100ba1e5ae001af624b9 before 8292f4f8dd1b005d0688d726261004f816ef730a; from c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bb before fd8547ebc187037cc69441a15c1441aeaab80f49; from f337a6a21e2fd67eadea471e93d05dd37baaa9be before fe42754b94a42d08cf9501790afc25c4f6a5f631 | CNA record |
Siemens RUGGEDCOM RST2428P siemens:ruggedcom_rst2428p (from the name) | before V3.1 | CISA ADP |
Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family siemens:scalance_xc_300_xr_300_xc_400_xr_500wg_xr_500_family (from the name) | all versions not affected | CISA ADP |
Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family siemens:scalance_xcm_xrm_xch_xrh_300_family (from the name) | before V3.1 | CISA ADP |
Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem siemens:simatic_s7_1500_tm_mfp_gnu_linux_subsystem (from the name) | before V1.1.1 | CISA ADP |
linux linux_kernel linux:linux_kernel | from 5.15.156 before 5.15.158; from 6.1.87 before 6.1.90; from 6.6.28 before 6.6.30; from 6.8.7 before 6.8.9; 6.9; 6.9 | NVD |
debian debian_linux debian:debian_linux | 10.0 | NVD |
References
- https://git.kernel.org/stable/c/af6d6a923b40bf6471e44067ac61cc5814b48e7fpatch
- https://git.kernel.org/stable/c/36b32816fbab267611f073223f1b0b816ec5920fpatch
- https://git.kernel.org/stable/c/38f17d1fbb5bfb56ca1419e2d06376d57a9396f9patch
- https://git.kernel.org/stable/c/8292f4f8dd1b005d0688d726261004f816ef730apatch
- https://git.kernel.org/stable/c/fd8547ebc187037cc69441a15c1441aeaab80f49patch
- https://git.kernel.org/stable/c/fe42754b94a42d08cf9501790afc25c4f6a5f631patch
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlmailing-list, third-party-advisory
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.