// For flags

CVE-2024-35996

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

Severity Score

"-"
*CVSS v-

Exploit Likelihood

*EPSS

Affected Versions

*CPE

Public Exploits

0
*Multiple Sources

Exploited in Wild

-
*KEV

Decision

Track
*SSVC
Descriptions

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.

En el kernel de Linux, se resolvió la siguiente vulnerabilidad: cpu: vuelva a habilitar las mitigaciones de CPU de forma predeterminada para arquitecturas !X86. Cambie el nombre de x86 a CPU_MITIGATION, defínalo en código genérico y fuércelo para todas las arquitecturas con excepción de x86. Una confirmación reciente para desactivar las mitigaciones de forma predeterminada si SPECULATION_MITIGATION=n pasó por alto que "cpu_mitigations" es completamente genérico, mientras que SPECULATION_MITIGATIONS es específico de x86. Cambie el nombre de SPECULATIVE_MITIGATION de x86 en lugar de conservar ambos y haga que seleccione CPU_MITIGATION, ya que tener dos configuraciones para lo mismo es innecesario y confuso. Esto también permitirá que x86 use la perilla para administrar mitigaciones que no están estrictamente relacionadas con la ejecución especulativa. Utilice otro Kconfig para comunicar al código común que CPU_MITIGACIONES ya está definida en lugar de que el menú de x86 dependa de CPU_MITIGACIONES comunes. Esto permite mantener un único punto de contacto para todas las mitigaciones de x86, y no está claro que otras arquitecturas *quieran* permitir deshabilitar las mitigaciones en tiempo de compilación.

*Credits: N/A
CVSS Scores
Attack Vector
-
Attack Complexity
-
Privileges Required
-
User Interaction
-
Scope
-
Confidentiality
-
Integrity
-
Availability
-
* Common Vulnerability Scoring System
SSVC
  • Decision:Track
Exploitation
None
Automatable
No
Tech. Impact
Partial
* Organization's Worst-case Scenario
Timeline
  • 2024-05-17 CVE Reserved
  • 2024-05-20 CVE Published
  • 2024-05-21 EPSS Updated
  • 2024-11-05 CVE Updated
  • ---------- Exploited in Wild
  • ---------- KEV Due Date
  • ---------- First Exploit
CWE
CAPEC
Affected Vendors, Products, and Versions
Vendor Product Version Other Status
Vendor Product Version Other Status <-- --> Vendor Product Version Other Status
Linux
Search vendor "Linux"
 Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
 >= 5.15.156 < 5.15.158
Search vendor "Linux" for product "Linux Kernel" and version " >= 5.15.156 < 5.15.158"
en
Affected
Linux
Search vendor "Linux"
 Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
 >= 6.1.87 < 6.1.90
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.1.87 < 6.1.90"
en
Affected
Linux
Search vendor "Linux"
 Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
 >= 6.6.28 < 6.6.30
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.6.28 < 6.6.30"
en
Affected
Linux
Search vendor "Linux"
 Linux Kernel
Search vendor "Linux" for product "Linux Kernel"
 >= 6.8.7 < 6.8.9
Search vendor "Linux" for product "Linux Kernel" and version " >= 6.8.7 < 6.8.9"
en
Affected