CVE-2024-35996

cpu: Re-enable CPU mitigations by default for !X86 architectures

MEDIUM
5.5
CVSS Score
Published: May 20, 2024 at 09:47 AM UTC
Updated: October 15, 2026 at 01:18 AM UTC
8 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC S7-1500 TM MFP

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.15.156 ≤ v < 5.15.1586.1.87 ≤ v < 6.1.906.6.28 ≤ v < 6.6.306.8.7 ≤ v < 6.8.92978ee7c973ce81b6e51100ba1e5ae001af624b930da4180fd768973189dc364648f9c436e57b01d5.15.1566.1.876.6.286.8.76.96.9 rc46.9 rc570688450dddaf91e12fd4fc625da3297025932c99c09773917fbb77dff85b433e1e89123fc5fb530c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bbf337a6a21e2fd67eadea471e93d05dd37baaa9be
Vendor states this is fixed in 36b32816fbab267611f073223f1b0b816ec5920f (fixed)
Vendor states this is fixed in 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9 (fixed)
Vendor states this is fixed in 8292f4f8dd1b005d0688d726261004f816ef730a (fixed)
Vendor states this is fixed in af6d6a923b40bf6471e44067ac61cc5814b48e7f (fixed)
Vendor states this is fixed in fd8547ebc187037cc69441a15c1441aeaab80f49 (fixed)
Vendor states this is fixed in fe42754b94a42d08cf9501790afc25c4f6a5f631 (fixed)
Affected range stops below 5.15.158, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.1.90, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.6.30, so it looks safe — our inference, not a vendor statement
Affected range stops below 6.8.9, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement
v < V3.1
Affected range stops below V3.1, so it looks safe — our inference, not a vendor statement

References (9)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/36b32816fbab267611f073223f1b0b816ec5920f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/38f17d1fbb5bfb56ca1419e2d06376d57a9396f9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/8292f4f8dd1b005d0688d726261004f816ef730a
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/af6d6a923b40bf6471e44067ac61cc5814b48e7f
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fd8547ebc187037cc69441a15c1441aeaab80f49
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/fe42754b94a42d08cf9501790afc25c4f6a5f631
Mailing ListThird Party Advisory
Source: af854a3a-2127-422b-91ae-364da2661108
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
Source: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
https://cert-portal.siemens.com/productcert/html/ssa-265688.html

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card