CVE-2024-35996

Medium

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.

SeverityMedium
CVSS5.5
Exploit probability—
ProductLinux Kernel
PublishedMay 20, 2024
First seenMay 20, 2024

How to fix

Update
  • linux linux_kernel5.15.158, 6.1.90, 6.6.30, 6.8.9 or later

Affected products

ProductAffected versionsFixed in
linux linux_kernel5.15.156 ≤ v < 5.15.158, 6.1.87 ≤ v < 6.1.90, 6.6.28 ≤ v < 6.6.30, 6.8.7 ≤ v < 6.8.9, 6.95.15.158, 6.1.90, 6.6.30, 6.8.9
debian debian_linux10.0—

Check your version

Choose the product and enter the version you run to see whether it falls in the affected range.

In the Intelligence 360 plan

Attack Surface Management

See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.

CVE-2024-35996 · Linux Kernel · Dark Radar