CVE-2024-50193high

CVE-2024-50193: fallo de gravedad alta en Linux

x86/entry_32: Clear CPU buffers after register restore in NMI return

Publicada el · Actualizada el

21Vexday Risk Score

Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.

ssvc Trackcvss 7.1epss 0.2%
probabilidad de explotación
0.2%top 89% de las CVE
explotación observada
noninguna fuente lo reporta
In the Linux kernel, the following vulnerability has been resolved: x86/entry_32: Clear CPU buffers after register restore in NMI return CPU buffers are currently cleared after call to exc_nmi, but before register state is restored. This may be okay for MDS mitigation but not for RDFS. Because RDFS mitigation requires CPU buffers to be cleared when registers don't have any sensitive data. Move CLEAR_CPU_BUFFERS after RESTORE_ALL_NMI.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Productos afectados
Linux · Linux
CVEs relacionadas — Linux

En el mismo producto, de las más peligrosas a las menos.

CVE-2024-53197HIGHALSA: usb-audio: Fix potential out-of-bound accesses for Extigy and Mbox devicesEPSS 4.1%KEVCVE-2026-31431HIGHcrypto: algif_aead - Revert to operating out-of-placeEPSS 3.4%KEVCVE-2024-53104HIGHmedia: uvcvideo: Skip parsing frames of type UVC_VS_UNDEFINED in uvc_parse_formatEPSS 3.4%KEVCVE-2025-39682CRITICALtls: fix handling of zero-length records on the rx_listEPSS 2.9%KEVCVE-2024-36971HIGHnet: fix __dst_negative_advice() raceEPSS 2.7%KEVCVE-2024-53150HIGHALSA: usb-audio: Fix out of bounds reads when finding clock sourcesEPSS 1.4%KEV
Referencias
https://git.kernel.org/stable/c/227358e89703c344008119be7e8ffa3fdb5b92dehttps://git.kernel.org/stable/c/43778de19d2ef129636815274644b9c16e78c66bhttps://git.kernel.org/stable/c/48a2440d0f20c826b884e04377ccc1e4696c84e9https://git.kernel.org/stable/c/64adf22c4bc73ede920baca5defefb70f190cdbchttps://git.kernel.org/stable/c/6f44a5fc15b5cece0785bc07453db77d99b0a6dehttps://git.kernel.org/stable/c/b6400eb0b347821efc57760221f8fb6d63b9548ahttps://lists.debian.org/debian-lts-announce/2025/01/msg00001.htmlhttps://lists.debian.org/debian-lts-announce/2025/03/msg00002.html