[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025022635-CVE-2024-57983-d9c0@gregkh>
Date: Wed, 26 Feb 2025 18:05:42 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-57983: mailbox: th1520: Fix memory corruption due to incorrect array size
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
mailbox: th1520: Fix memory corruption due to incorrect array size
The functions th1520_mbox_suspend_noirq and th1520_mbox_resume_noirq are
intended to save and restore the interrupt mask registers in the MBOX
ICU0. However, the array used to store these registers was incorrectly
sized, leading to memory corruption when accessing all four registers.
This commit corrects the array size to accommodate all four interrupt
mask registers, preventing memory corruption during suspend and resume
operations.
The Linux kernel CVE team has assigned CVE-2024-57983 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.13 with commit 5d4d263e1c6b6b18acb4d67fd3b9af71b7404924 and fixed in 6.13.2 with commit 2cd12c7fba59f30369e8647a2b726c7280903304
Issue introduced in 6.13 with commit 5d4d263e1c6b6b18acb4d67fd3b9af71b7404924 and fixed in 6.14-rc1 with commit db049866943a38bf46a34fa120d526663339d7a5
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-57983
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/mailbox/mailbox-th1520.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/2cd12c7fba59f30369e8647a2b726c7280903304
https://git.kernel.org/stable/c/db049866943a38bf46a34fa120d526663339d7a5
Powered by blists - more mailing lists