From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 51FC114A91 for ; Mon, 8 Dec 2025 01:20:50 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765156850; cv=none; b=XnAM9UJXca04cokU8lTi75MtEXGM2zbS18rGIgdrtMmMEWP+xjh4xnNF/OwsV+5UFyW0Ph7DXmIMP8mMV7l//Kf2gPKnkwmrIsjuDUXpskO/eL3EyJRLL66iFHcazKlBWnlgecT/9MJTBXD+vSKO8I2jdP7tjVra+rrGCqXPzZQ= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1765156850; c=relaxed/simple; bh=XTA86g130byRc+nc/2YONbiMzrDagRnl06jpU3IRqkc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=lcbYWucKgAohaNHiUlYsu1WMZqLt/R/G0JjHBJGnoKiJouPLI7Bmg75j3vw9tF6PJo0xNm5fUHhQK6C86T2mxtnQDfuuRbTpoPle7lS0iqLgos+mpCmHFEF/nNP2g28GftLVm7A1iRUChpEx+bpeDMTc4WkQi8HzE5z3tX5kaDk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=ltUuDany; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="ltUuDany" Received: by smtp.kernel.org (Postfix) with ESMTPSA id E352AC4CEFB; Mon, 8 Dec 2025 01:20:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1765156850; bh=XTA86g130byRc+nc/2YONbiMzrDagRnl06jpU3IRqkc=; h=From:To:Cc:Subject:Date:Reply-To:From; b=ltUuDanycvKKEB5NlvNE/iK22To0xy88aDC6mgA+wTGlu18ZJpEyNBYUjFMiiARPq bFrh57E1g4yiPl+JMWjlIbPawUDtgtT3utQE1SjTr/pyUVLKHN7EwKqNSBaUi9PVOo 3+vyt2t+mKbEAYZ9EvkXtpWoYssNpDE4iDoi+wUA= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2023-53746: s390/vfio-ap: fix memory leak in vfio_ap device driver Date: Mon, 8 Dec 2025 10:19:45 +0900 Message-ID: <2025120841-CVE-2023-53746-cbfd@gregkh> X-Mailer: git-send-email 2.52.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=3222; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=TxeNCRxWF/+j060JbGBLfBbhXl5jARrRtjCxlOzRUyA=; b=owGbwMvMwCRo6H6F97bub03G02pJDJlm6uuW7BGfUh1hryP1eH6HY8mEM3stzIXn9fa0XUvO9 D/S6GLdEcvCIMjEICumyPJlG8/R/RWHFL0MbU/DzGFlAhnCwMUpABPJ28cwT+NX59Johttmxzk/ bLO/oeJplP9emWGuTLXtjeairtjwh0fDQw16ZjVU+L0BAA== X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: s390/vfio-ap: fix memory leak in vfio_ap device driver The device release callback function invoked to release the matrix device uses the dev_get_drvdata(device *dev) function to retrieve the pointer to the vfio_matrix_dev object in order to free its storage. The problem is, this object is not stored as drvdata with the device; since the kfree function will accept a NULL pointer, the memory for the vfio_matrix_dev object is never freed. Since the device being released is contained within the vfio_matrix_dev object, the container_of macro will be used to retrieve its pointer. The Linux kernel CVE team has assigned CVE-2023-53746 to this issue. Affected and fixed versions =========================== Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 5.4.240 with commit 5195de1d5f66b276683240a896783f7f43c4f664 Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 5.10.177 with commit ee17dea3072dec0bc34399a32fa884e26342e4ea Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 5.15.106 with commit aa2bff25e9bb10c935c7ffe3d5f5975bdccb1749 Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 6.1.23 with commit 6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67 Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 6.2.10 with commit 7b6a02f5bf15931464c79dfd487c57f76aae3496 Issue introduced in 4.20 with commit 1fde573413b549d52183382e639c1d6ce88f5959 and fixed in 6.3 with commit 8f8cf767589f2131ae5d40f3758429095c701c84 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-53746 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/s390/crypto/vfio_ap_drv.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/5195de1d5f66b276683240a896783f7f43c4f664 https://git.kernel.org/stable/c/ee17dea3072dec0bc34399a32fa884e26342e4ea https://git.kernel.org/stable/c/aa2bff25e9bb10c935c7ffe3d5f5975bdccb1749 https://git.kernel.org/stable/c/6a40fda14b4be3e38f03cc42ffd4efbc64fb3e67 https://git.kernel.org/stable/c/7b6a02f5bf15931464c79dfd487c57f76aae3496 https://git.kernel.org/stable/c/8f8cf767589f2131ae5d40f3758429095c701c84