linux-cve-announce - CVE-2023-54043: iommufd: Do not add the same hwpt to the ioas->hwpt

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: <2025122422-CVE-2023-54043-16c8@gregkh>
Date: Wed, 24 Dec 2025 13:26:36 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54043: iommufd: Do not add the same hwpt to the ioas->hwpt_list twice

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

iommufd: Do not add the same hwpt to the ioas->hwpt_list twice

The hwpt is added to the hwpt_list only during its creation, it is never
added again. This hunk is some missed leftover from rework. Adding it
twice will corrupt the linked list in some cases.

It effects HWPT specific attachment, which is something the test suite
cannot cover until we can create a legitimate struct device with a
non-system iommu "driver" (ie we need the bus removed from the iommu code)

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


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

	Issue introduced in 6.2 with commit e8d57210035b6377d424ba964961892d01127cf6 and fixed in 6.2.3 with commit c44adefdcf472f946f0632f4e0ddcbf3e00b8516
	Issue introduced in 6.2 with commit e8d57210035b6377d424ba964961892d01127cf6 and fixed in 6.3 with commit b4ff830eca097df51af10a9be29e8cc817327919

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-54043
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/iommu/iommufd/device.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/c44adefdcf472f946f0632f4e0ddcbf3e00b8516
	https://git.kernel.org/stable/c/b4ff830eca097df51af10a9be29e8cc817327919