CVE-2023-54043
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)
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A use-after-free or list corruption bug in the Linux kernel's iommufd subsystem where the same hardware pagetable (hwpt) could be added to the ioas->hwpt_list twice, corrupting the linked list.
Root
Cause
The vulnerability resides in the Linux kernel's iommufd subsystem. During rework of the code, a leftover hunk caused the same hardware pagetable (hwpt) to be added to the ioas->hwpt_list linked list twice. The hwpt is normally added to this list only during its creation, but the erroneous code path allowed a second addition. This double insertion corrupts the linked list, leading to undefined behavior, including potential use-after-free or memory corruption [1].
Exploitation
Exploitation requires the ability to trigger the specific HWPT attachment path that exercises this bug. The kernel developers note that this path is not covered by the existing test suite because it requires a legitimate struct device with a non-system IOMMU driver (i.e., a bus removed from the IOMMU code). In practice, an attacker would need local access and the ability to create or manipulate IOMMU mappings in a way that triggers the double list add [1].
Impact
An attacker who successfully triggers this bug could corrupt kernel memory, potentially leading to a denial of service (system crash) or, in more severe cases, privilege escalation if the corruption is leveraged to overwrite sensitive data structures. The exact impact depends on the kernel configuration and the state of the linked list at the time of corruption.
Mitigation
The fix is included in the Linux kernel stable tree commit referenced in the advisory [1]. Users should apply the latest stable kernel updates from their distribution. No workaround is available; the vulnerability is fixed by removing the erroneous leftover code.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
2c44adefdcf47b4ff830eca09Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
2News mentions
0No linked articles in our index yet.