# CVE-2023-54043: iommufd: Do not add the same hwpt to the ioas->hwpt_list twice

> A logic error in the Linux kernel iommufd subsystem can corrupt a linked list, potentially leading to system instability or denial of service.

- **Severity:** High 8.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** BELL-CVE-2023-54043, GHSA-hwvv-764m-j5cv, UBUNTU-CVE-2023-54043

## What is CVE-2023-54043?

CVE-2023-54043 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2023-54043?


## How do I fix CVE-2023-54043?

Apply the vendor's patch.

## Is CVE-2023-54043 being exploited?

There is no known exploitation of CVE-2023-54043 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-54043 and fix it if it is affected.

What it is: CVE-2023-54043 is a high-severity memory corruption vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-54043 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-54043/ (Markdown: https://insights.sbomify.com/CVE-2023-54043/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-54043
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-54043
- OSV: https://osv.dev/vulnerability/CVE-2023-54043

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-54043/
Summaries are generated and may contain mistakes; the official description above is the record.