You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE has been marked Rejected in the CVE List. These CVEs are stored in the NVD, but do not show up in search results by default.
Description
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
Title: kernel de Linux
Description: En el kernel de Linux, se resolvió la siguiente vulnerabilidad: x86/reboot: VMCLEAR VMCS activos antes del reinicio de emergencia VMCLEAR VMCS activos antes de cualquier reinicio de emergencia, no solo si el kernel puede realizar una ejecución kexec en un nuevo kernel después de una falla. Según el SDM de Intel, la arquitectura VMX no requiere que la CPU vacíe la caché VMCS en INIT. Si un reinicio de emergencia no RESTABLECE las CPU, los VMCS almacenados en caché podrían, en teoría, conservarse y solo volver a escribirse en la memoria después de que se inicie el nuevo kernel, es decir, podrían dañar efectivamente la memoria después del reinicio. De manera oportunista, elimine la configuración del puntero global en NULL para que checkpatch esté contento.
CVE Modified by kernel.org3/11/2024 12:15:07 PM
Action
Type
Old Value
New Value
Changed
Description
In the Linux kernel, the following vulnerability has been resolved:
x86/reboot: VMCLEAR active VMCSes before emergency reboot
VMCLEAR active VMCSes before any emergency reboot, not just if the kernel
may kexec into a new kernel after a crash. Per Intel's SDM, the VMX
architecture doesn't require the CPU to flush the VMCS cache on INIT. If
an emergency reboot doesn't RESET CPUs, cached VMCSes could theoretically
be kept and only be written back to memory after the new kernel is booted,
i.e. could effectively corrupt memory after reboot.
Opportunistically remove the setting of the global pointer to NULL to make
checkpatch happy.
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Removed
Reference
Linux https://git.kernel.org/stable/c/1375d9600c38c231163de584656b07aef9a27b0d
Removed
Reference
Linux https://git.kernel.org/stable/c/65edea77d7006140c6290e7f46009d75e02d3273
Removed
Reference
Linux https://git.kernel.org/stable/c/b23c83ad2c638420ec0608a9de354507c41bec29
CVE Rejected by kernel.org3/11/2024 12:15:07 PM
Action
Type
Old Value
New Value
New CVE Received from kernel.org3/02/2024 5:15:47 PM
Action
Type
Old Value
New Value
Added
Description
In the Linux kernel, the following vulnerability has been resolved:
x86/reboot: VMCLEAR active VMCSes before emergency reboot
VMCLEAR active VMCSes before any emergency reboot, not just if the kernel
may kexec into a new kernel after a crash. Per Intel's SDM, the VMX
architecture doesn't require the CPU to flush the VMCS cache on INIT. If
an emergency reboot doesn't RESET CPUs, cached VMCSes could theoretically
be kept and only be written back to memory after the new kernel is booted,
i.e. could effectively corrupt memory after reboot.
Opportunistically remove the setting of the global pointer to NULL to make
checkpatch happy.
Added
Reference
Linux https://git.kernel.org/stable/c/1375d9600c38c231163de584656b07aef9a27b0d [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/65edea77d7006140c6290e7f46009d75e02d3273 [No types assigned]
Added
Reference
Linux https://git.kernel.org/stable/c/b23c83ad2c638420ec0608a9de354507c41bec29 [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2023-52514 NVD
Published Date: 03/02/2024 NVD
Last Modified: 03/11/2024
Source: kernel.org