CVE-2022-49610
MediumIn the Linux kernel, the following vulnerability has been resolved: KVM: VMX: Prevent RSB underflow before vmenter On VMX, there are some balanced returns between the time the guest's SPEC_CTRL value is written, and the vmenter. Balanced returns (matched by a preceding call) are usually ok, but it's at least theoretically possible an NMI with a deep call stack could empty the RSB before one of the returns. For maximum paranoia, don't allow *any* returns (balanced or otherwise) between the SPEC_CTRL write and the vmenter. [ bp: Fix 32-bit build. ]
CVSS 3.1 score
5.5
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected versions
Linux kernel versions
3.16.57,
4.4.168,
4.16
and later are affected. Fixed in
5.18.14,
5.19
and their respective stable series.
References
The following references provide additional information about CVE-2022-49610 including vendor advisories, patch commits, exploit details, and third-party analysis. Links are sourced from the NIST NVD database.
-
PatchKernel patch commithttps://git.kernel.org/stable/c/07853adc29a058c5fd143c14e5ac528448a72ed9
-
PatchKernel patch commithttps://git.kernel.org/stable/c/afd743f6dde87296c6f3414706964c491bb85862
Frequently asked questions
-
What is CVE-2022-49610?
CVE-2022-49610 is a Medium severity Linux kernel vulnerability with a CVSS score of 5.5 out of 10 . It affects Linux kernel versions from 3.16.57 onward and has been patched in 5.18.14 and 5.19. CVE-2022-49610 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
What is the CVSS score for CVE-2022-49610?
CVE-2022-49610 has a CVSS score of 5.5 out of 10, rated Medium severity (CVSS 3.1). The vector string is
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. -
Is there a patch available for CVE-2022-49610?
Yes — CVE-2022-49610 has been patched. Fixed versions include 5.18.14 and 5.19. If you are running Linux kernel 3.16.57 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2022-49610 actively exploited?
No — CVE-2022-49610 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.