[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025050155-CVE-2022-49883-ba54@gregkh>
Date: Thu, 1 May 2025 16:11:13 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-49883: KVM: x86: smm: number of GPRs in the SMRAM image depends on the image format
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
KVM: x86: smm: number of GPRs in the SMRAM image depends on the image format
On 64 bit host, if the guest doesn't have X86_FEATURE_LM, KVM will
access 16 gprs to 32-bit smram image, causing out-ouf-bound ram
access.
On 32 bit host, the rsm_load_state_64/enter_smm_save_state_64
is compiled out, thus access overflow can't happen.
The Linux kernel CVE team has assigned CVE-2022-49883 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.0 with commit b443183a25ab61840a12de92f8822849e017b9c8 and fixed in 6.0.8 with commit a7ebfbea0f52550d7cdf12c38f3f5eaa7b2b6494
Issue introduced in 6.0 with commit b443183a25ab61840a12de92f8822849e017b9c8 and fixed in 6.1 with commit 696db303e54f7352623d9f640e6c51d8fa9d5588
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-49883
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
arch/x86/kvm/emulate.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/a7ebfbea0f52550d7cdf12c38f3f5eaa7b2b6494
https://git.kernel.org/stable/c/696db303e54f7352623d9f640e6c51d8fa9d5588
Powered by blists - more mailing lists