CVE-2024-35801

{"id": "CVE-2024-35801", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 7.8, "attackVector": "LOCAL", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 1.8}]}, "published": "2024-05-17T14:15:12.827", "references": [{"url": "https://git.kernel.org/stable/c/10e4b5166df9ff7a2d5316138ca668b42d004422", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/1acbca933313aa866e39996904c9aca4d435c4cd", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/21c7c00dae55cb0e3810d5f9506b58f68475d41d", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/92b0f04e937665bde5768f3fcc622dcce44413d8", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}, {"url": "https://git.kernel.org/stable/c/b61e3b7055ac6edee4be071c52f48c26472d2624", "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}], "vulnStatus": "Awaiting Analysis", "weaknesses": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "description": [{"lang": "en", "value": "CWE-416"}]}], "descriptions": [{"lang": "en", "value": "In the Linux kernel, the following vulnerability has been resolved:\n\nx86/fpu: Keep xfd_state in sync with MSR_IA32_XFD\n\nCommit 672365477ae8 (\"x86/fpu: Update XFD state where required\") and\ncommit 8bf26758ca96 (\"x86/fpu: Add XFD state to fpstate\") introduced a\nper CPU variable xfd_state to keep the MSR_IA32_XFD value cached, in\norder to avoid unnecessary writes to the MSR.\n\nOn CPU hotplug MSR_IA32_XFD is reset to the init_fpstate.xfd, which\nwipes out any stale state. But the per CPU cached xfd value is not\nreset, which brings them out of sync.\n\nAs a consequence a subsequent xfd_update_state() might fail to update\nthe MSR which in turn can result in XRSTOR raising a #NM in kernel\nspace, which crashes the kernel.\n\nTo fix this, introduce xfd_set_state() to write xfd_state together\nwith MSR_IA32_XFD, and use it in all places that set MSR_IA32_XFD."}, {"lang": "es", "value": "En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: x86/fpu: mantenga xfd_state sincronizado con MSR_IA32_XFD Confirme 672365477ae8 (\"x86/fpu: actualice el estado de XFD cuando sea necesario\") y confirme 8bf26758ca96 (\"x86/fpu: agregue el estado de XFD a fpstate\") introdujo una variable xfd_state por CPU para mantener el valor MSR_IA32_XFD en cach\u00e9, a fin de evitar escrituras innecesarias en el MSR. En la conexi\u00f3n en caliente de la CPU, MSR_IA32_XFD se restablece a init_fpstate.xfd, lo que elimina cualquier estado obsoleto. Pero el valor xfd almacenado en cach\u00e9 por CPU no se restablece, lo que los desincroniza. Como consecuencia, un xfd_update_state() posterior podr\u00eda no actualizar el MSR, lo que a su vez puede provocar que XRSTOR genere un #NM en el espacio del kernel, lo que bloquea el kernel. Para solucionar este problema, introduzca xfd_set_state() para escribir xfd_state junto con MSR_IA32_XFD y util\u00edcelo en todos los lugares que configuren MSR_IA32_XFD."}], "lastModified": "2024-07-03T02:02:12.050", "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"}