cpu: Re-enable CPU mitigations by default for !X86 architectures (Linux Linux)
At a glance
- Source
- NVD
- EPSS
- EPSS 0.24 % · percentile 16 ()
- State
- PUBLISHED
- Published
- Updated
- Assigner
- Linux
- NVD status
- Modified
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.
References
- https://git.kernel.org/stable/c/af6d6a923b40bf6471e44067ac61cc5814b48e7f
- https://git.kernel.org/stable/c/36b32816fbab267611f073223f1b0b816ec5920f
- https://git.kernel.org/stable/c/38f17d1fbb5bfb56ca1419e2d06376d57a9396f9
- https://git.kernel.org/stable/c/8292f4f8dd1b005d0688d726261004f816ef730a
- https://git.kernel.org/stable/c/fd8547ebc187037cc69441a15c1441aeaab80f49
- https://git.kernel.org/stable/c/fe42754b94a42d08cf9501790afc25c4f6a5f631
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
Scores
| Version | Score | Vector | Scored by |
|---|---|---|---|
| CVSS 3.1 | MEDIUM 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H | NVD · nvd@nist.gov (Primary) |
European references
- ENISA EUVD · EUVD-2024-35714
- GCVE · GCVE-0-2024-35996
CERT-FR advisories
- CERTFR-2024-AVI-0694 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2024-AVI-0667 — Multiples vulnérabilités dans le noyau Linux d'Ubuntu · cert.ssi.gouv.fr
- CERTFR-2024-AVI-0527 — Multiples vulnérabilités dans le noyau Linux de Debian LTS · cert.ssi.gouv.fr
Affected configurations (NVD CPE)
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 5.15.156 < 5.15.158cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 6.1.87 < 6.1.90cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 6.6.28 < 6.6.30cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*≥ 6.8.7 < 6.8.9cpe:2.3:o:linux:linux_kernel:6.9:rc4:*:*:*:*:*:*cpe:2.3:o:linux:linux_kernel:6.9:rc5:*:*:*:*:*:*cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
Affected products
| Product | Versions |
|---|---|
| Linux · Linux | affected 30da4180fd768973189dc364648f9c436e57b01d < af6d6a923b40bf6471e44067ac61cc5814b48e7f ; affected 70688450dddaf91e12fd4fc625da3297025932c9 < 36b32816fbab267611f073223f1b0b816ec5920f ; affected 9c09773917fbb77dff85b433e1e89123fc5fb530 < 38f17d1fbb5bfb56ca1419e2d06376d57a9396f9 ; affected 2978ee7c973ce81b6e51100ba1e5ae001af624b9 < 8292f4f8dd1b005d0688d726261004f816ef730a ; affected c4a9babdd5d5a41a74269a2e1aa1647b1b4c45bb < fd8547ebc187037cc69441a15c1441aeaab80f49 ; affected f337a6a21e2fd67eadea471e93d05dd37baaa9be < fe42754b94a42d08cf9501790afc25c4f6a5f631 |
| Linux · Linux | affected 5.15.156 < 5.15.158 ; affected 6.1.87 < 6.1.90 ; affected 6.6.28 < 6.6.30 ; affected 6.8.7 < 6.8.9 |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| CERT-FR (ANSSI) | Licence Ouverte / Etalab 2.0 |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |