Answer in brief
CVE-2024-35996 records a Unknown severity vulnerability in cpu: Re-enable CPU mitigations by default for !X86 architectures. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/RUGGEDCOM RST2428P (generic), Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 family (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=30da4180fd768973189dc364648f9c436e57b01d <af6d6a923b40bf6471e44067ac61cc5814b48e7f || >=70688450dddaf91e12fd4fc625da3297025932c9 <36b32816fbab267611f073223f1b0b816ec5920f || >=9c09773917fbb77dff85b433e1e89123fc5fb530 <38f17d1fbb5bfb56ca1419e2d06376d57a9396f9 || >=2978ee7c973ce81b6e51100ba1e5ae001af624b9 <8292f4f8dd1b005d0688d726261004f816ef730a || >=c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bb <fd8547ebc187037cc69441a15c1441aeaab80f49 || >=f337a6a21e2fd67eadea471e93d05dd37baaa9be <fe42754b94a42d08cf9501790afc25c4f6a5f631 | af6d6a923b40bf6471e44067ac61cc5814b48e7f, 36b32816fbab267611f073223f1b0b816ec5920f, 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9, 8292f4f8dd1b005d0688d726261004f816ef730a, fd8547ebc187037cc69441a15c1441aeaab80f49, fe42754b94a42d08cf9501790afc25c4f6a5f631 |
| Linux/Linuxgeneric | >=5.15.156 <5.15.158 || >=6.1.87 <6.1.90 || >=6.6.28 <6.6.30 || >=6.8.7 <6.8.9 | 5.15.158, 6.1.90, 6.6.30, 6.8.9 |
| Siemens/RUGGEDCOM RST2428Pgeneric | >=0 <V3.1 | V3.1 |
| Siemens/SCALANCE XCM-/XRM-/XCH-/XRH-300 familygeneric | >=0 <V3.1 | V3.1 |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <V1.1.1 | V1.1.1 |
Published upstream
May 20, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.