linux: In the Linux kernel, the following vulnerability has been resolved: cpu: Re-enable CPU mitigations by default for !X...
CVE-2024-35996 is fixed in 22 products on 1 platform, first by DEBIAN-CVE-2024-35996, released May 20, 2024. It is not reported as exploited. Patch Radar priority: Routine.
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.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| bpftool · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| bpftool-debuginfo · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-debuginfo · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-debuginfo-common-aarch64 · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-debuginfo-common-x86_64 · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-devel · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-headers · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-libbpf · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-libbpf-devel · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-libbpf-static · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-livepatch-6.1.90-99.173 · amzn 2023 | 1.0-0.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-modules-extra · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-modules-extra-common · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-tools · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-tools-debuginfo · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| kernel-tools-devel · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| linux · Debian 12.15 (bookworm) | 6.1.90-1 | DEBIAN-CVE-2024-35996 | May 20, 2024 |
| linux · Debian 13.5 (trixie) | 6.8.9-1 | DEBIAN-CVE-2024-35996 | May 20, 2024 |
| linux · Debian 14 | 6.8.9-1 | DEBIAN-CVE-2024-35996 | May 20, 2024 |
| perf · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| perf-debuginfo · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| python3-perf · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
| python3-perf-debuginfo · amzn 2023 | 6.1.90-99.173.amzn2023 | ALAS2023-2024-695 | Aug 1, 2024 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.