linux-cve-announce - CVE-2023-53003: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025032712-CVE-2023-53003-8256@gregkh>
Date: Thu, 27 Mar 2025 17:43:50 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2023-53003: EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

EDAC/qcom: Do not pass llcc_driv_data as edac_device_ctl_info's pvt_info

The memory for llcc_driv_data is allocated by the LLCC driver. But when
it is passed as the private driver info to the EDAC core, it will get freed
during the qcom_edac driver release. So when the qcom_edac driver gets probed
again, it will try to use the freed data leading to the use-after-free bug.

Hence, do not pass llcc_driv_data as pvt_info but rather reference it
using the platform_data pointer in the qcom_edac driver.

The Linux kernel CVE team has assigned CVE-2023-53003 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 4.20 with commit 27450653f1db0b9d5b5048a246c850c52ee4aa61 and fixed in 5.4.231 with commit 66e10d5f399629ef7877304d9ba2b35d0474e7eb
	Issue introduced in 4.20 with commit 27450653f1db0b9d5b5048a246c850c52ee4aa61 and fixed in 5.10.166 with commit 76d9ebb7f0bc10fbc78b6d576751552edf743968
	Issue introduced in 4.20 with commit 27450653f1db0b9d5b5048a246c850c52ee4aa61 and fixed in 5.15.91 with commit bff5243bd32661cf9ce66f6d9210fc8f89bda145
	Issue introduced in 4.20 with commit 27450653f1db0b9d5b5048a246c850c52ee4aa61 and fixed in 6.1.9 with commit 6f0351d0c311951b8b3064db91e61841e85b2b96
	Issue introduced in 4.20 with commit 27450653f1db0b9d5b5048a246c850c52ee4aa61 and fixed in 6.2 with commit 977c6ba624f24ae20cf0faee871257a39348d4a9

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-2023-53003
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/edac/qcom_edac.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/66e10d5f399629ef7877304d9ba2b35d0474e7eb
	https://git.kernel.org/stable/c/76d9ebb7f0bc10fbc78b6d576751552edf743968
	https://git.kernel.org/stable/c/bff5243bd32661cf9ce66f6d9210fc8f89bda145
	https://git.kernel.org/stable/c/6f0351d0c311951b8b3064db91e61841e85b2b96
	https://git.kernel.org/stable/c/977c6ba624f24ae20cf0faee871257a39348d4a9