[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024120248-CVE-2024-53110-3bff@gregkh>
Date: Mon, 2 Dec 2024 14:52:49 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53110: vp_vdpa: fix id_table array not null terminated error
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
vp_vdpa: fix id_table array not null terminated error
Allocate one extra virtio_device_id as null terminator, otherwise
vdpa_mgmtdev_get_classes() may iterate multiple times and visit
undefined memory.
The Linux kernel CVE team has assigned CVE-2024-53110 to this issue.
Affected and fixed versions
===========================
Issue introduced in 5.19 with commit ffbda8e9df10 and fixed in 6.1.119 with commit 870d68fe17b5
Issue introduced in 5.19 with commit ffbda8e9df10 and fixed in 6.6.63 with commit c4d64534d4b1
Issue introduced in 5.19 with commit ffbda8e9df10 and fixed in 6.11.10 with commit 0a886489d274
Issue introduced in 5.19 with commit ffbda8e9df10 and fixed in 6.12 with commit 4e39ecadf1d2
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-53110
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:
drivers/vdpa/virtio_pci/vp_vdpa.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/870d68fe17b5d9032049dcad98b5781a344a8657
https://git.kernel.org/stable/c/c4d64534d4b1c47d2f1ce427497f971ad4735aae
https://git.kernel.org/stable/c/0a886489d274596ad1a80789d3a773503210a615
https://git.kernel.org/stable/c/4e39ecadf1d2a08187139619f1f314b64ba7d947
Powered by blists - more mailing lists