mirror of
https://github.com/fkie-cad/nvd-json-data-feeds.git
synced 2025-06-19 17:31:42 +00:00
28 lines
1.7 KiB
JSON
28 lines
1.7 KiB
JSON
![]() |
{
|
||
|
"id": "CVE-2023-52874",
|
||
|
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
|
||
|
"published": "2024-05-21T16:15:24.157",
|
||
|
"lastModified": "2024-05-21T16:53:56.550",
|
||
|
"vulnStatus": "Awaiting Analysis",
|
||
|
"descriptions": [
|
||
|
{
|
||
|
"lang": "en",
|
||
|
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/tdx: Zero out the missing RSI in TDX_HYPERCALL macro\n\nIn the TDX_HYPERCALL asm, after the TDCALL instruction returns from the\nuntrusted VMM, the registers that the TDX guest shares to the VMM need\nto be cleared to avoid speculative execution of VMM-provided values.\n\nRSI is specified in the bitmap of those registers, but it is missing\nwhen zeroing out those registers in the current TDX_HYPERCALL.\n\nIt was there when it was originally added in commit 752d13305c78\n(\"x86/tdx: Expand __tdx_hypercall() to handle more arguments\"), but was\nlater removed in commit 1e70c680375a (\"x86/tdx: Do not corrupt\nframe-pointer in __tdx_hypercall()\"), which was correct because %rsi is\nlater restored in the \"pop %rsi\". However a later commit 7a3a401874be\n(\"x86/tdx: Drop flags from __tdx_hypercall()\") removed that \"pop %rsi\"\nbut forgot to add the \"xor %rsi, %rsi\" back.\n\nFix by adding it back."
|
||
|
}
|
||
|
],
|
||
|
"metrics": {},
|
||
|
"references": [
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/2191950d35d8f81620ea8d4e04d983f664fe3a8a",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/5d092b66119d774853cc9308522620299048a662",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
},
|
||
|
{
|
||
|
"url": "https://git.kernel.org/stable/c/de4c5bacca4f50233f1f791bec9eeb4dee1b14cd",
|
||
|
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
|
||
|
}
|
||
|
]
|
||
|
}
|