[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024072920-CVE-2024-41028-d1bd@gregkh>
Date: Mon, 29 Jul 2024 16:32:23 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-41028: platform/x86: toshiba_acpi: Fix array out-of-bounds access
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
platform/x86: toshiba_acpi: Fix array out-of-bounds access
In order to use toshiba_dmi_quirks[] together with the standard DMI
matching functions, it must be terminated by a empty entry.
Since this entry is missing, an array out-of-bounds access occurs
every time the quirk list is processed.
Fix this by adding the terminating empty entry.
The Linux kernel CVE team has assigned CVE-2024-41028 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.1 with commit 3cb1f40dfdc3 and fixed in 6.1.100 with commit e030aa6c9726
Issue introduced in 6.1 with commit 3cb1f40dfdc3 and fixed in 6.6.41 with commit 639868f1cb87
Issue introduced in 6.1 with commit 3cb1f40dfdc3 and fixed in 6.9.10 with commit 0d71da43d6b7
Issue introduced in 6.1 with commit 3cb1f40dfdc3 and fixed in 6.10 with commit b6e02c6b0377
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-41028
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/platform/x86/toshiba_acpi.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/e030aa6c972641cb069086a8c7a0f747653e472a
https://git.kernel.org/stable/c/639868f1cb87b683cf830353bbee0c4078202313
https://git.kernel.org/stable/c/0d71da43d6b7916d36cf1953d793da80433c50bf
https://git.kernel.org/stable/c/b6e02c6b0377d4339986e07aeb696c632cd392aa
Powered by blists - more mailing lists