cpu: Re-enable CPU mitigations by default for !X86 architectures
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.15.158, 6.1.90, 6.6.30, 6.8.9
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 30da4180fd768973189dc364648f9c436e57b01d · fixed in af6d6a923b40bf6471e44067ac61cc5814b48e7f; From 70688450dddaf91e12fd4fc625da3297025932c9 · fixed in 36b32816fbab267611f073223f1b0b816ec5920f; From 9c09773917fbb77dff85b433e1e89123fc5fb530 · fixed in 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9; From 2978ee7c973ce81b6e51100ba1e5ae001af624b9 · fixed in 8292f4f8dd1b005d0688d726261004f816ef730a; From c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bb · fixed in fd8547ebc187037cc69441a15c1441aeaab80f49; From f337a6a21e2fd67eadea471e93d05dd37baaa9be · fixed in fe42754b94a42d08cf9501790afc25c4f6a5f631
- Linux Linux
From 5.15.156 · fixed in 5.15.158; From 6.1.87 · fixed in 6.1.90; From 6.6.28 · fixed in 6.6.30; From 6.8.7 · fixed in 6.8.9
- KernelLinux
From 5.15.156 · fixed in 5.15.158; From 6.1.87 · fixed in 6.1.90; From 6.6.28 · fixed in 6.6.30; From 6.8.7 · fixed in 6.8.9