From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-53228: riscv: kvm: Fix out-of-bounds array access
Date: Fri, 27 Dec 2024 14:53:14 +0100 [thread overview]
Message-ID: <2024122736-CVE-2024-53228-0c5f@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
riscv: kvm: Fix out-of-bounds array access
In kvm_riscv_vcpu_sbi_init() the entry->ext_idx can contain an
out-of-bound index. This is used as a special marker for the base
extensions, that cannot be disabled. However, when traversing the
extensions, that special marker is not checked prior indexing the
array.
Add an out-of-bounds check to the function.
The Linux kernel CVE team has assigned CVE-2024-53228 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.7 with commit 56d8a385b60556019ecb45d6098830c9ef6a13e0 and fixed in 6.11.11 with commit 3c49e1084a5df99807fc43dd318c491e6cbaa168
Issue introduced in 6.7 with commit 56d8a385b60556019ecb45d6098830c9ef6a13e0 and fixed in 6.12.2 with commit b1af648f0d610665c956ea4604d9f797e5c7e991
Issue introduced in 6.7 with commit 56d8a385b60556019ecb45d6098830c9ef6a13e0 and fixed in 6.13-rc1 with commit 332fa4a802b16ccb727199da685294f85f9880cb
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-2024-53228
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/riscv/kvm/vcpu_sbi.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/3c49e1084a5df99807fc43dd318c491e6cbaa168
https://git.kernel.org/stable/c/b1af648f0d610665c956ea4604d9f797e5c7e991
https://git.kernel.org/stable/c/332fa4a802b16ccb727199da685294f85f9880cb
reply other threads:[~2024-12-27 13:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2024122736-CVE-2024-53228-0c5f@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.