# iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode

CVE record · `CVE-2026-43130`

- **Identifiers:** `CVE-2026-43130`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 6 May 2026
- **Updated:** 6 Nov 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 6 May 2026, 11:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `f873b85ec762c5a6abe94a7ddb31df5d3ba07d85 to before 581ce094d9eafb78ec4f9de77bd24b780c151236` (git)
  - affected: `d70f1c85113cd8c2aa8373f491ca5d1b22ec0554 to before e2c78c69f8faf2885ea4ceee08c71ac738f401a0` (git)
  - affected: `34a7b30f56d30114bf4d436e4dc793afe326fbcf to before ead67d0378e90f419e385a43af29435242d80c12` (git)
  - affected: `2b74b2a92e524d7c8dec8e02e95ecf18b667c062 to before 01aed2f1d7cb8fdf4c60c5bb4727608cb82b401d` (git)
  - affected: `4fc82cd907ac075648789cc3a00877778aa1838b to before 9813306610d0d718c863aaa70928bf57d7570ec0` (git)
  - affected: `4fc82cd907ac075648789cc3a00877778aa1838b to before 9deaacc8dcaddb6ddc5b52e1e63b457450ec0f94` (git)
  - affected: `4fc82cd907ac075648789cc3a00877778aa1838b to before 0da6697e577023d8867c7beb2d16a22510e4eea9` (git)
  - affected: `4fc82cd907ac075648789cc3a00877778aa1838b to before 10e60d87813989e20eac1f3eda30b3bae461e7f9` (git)
  - affected: `c04f2780919f20e2cc4846764221f5e802555868` (git)
  - affected: `025bc6b41e020aeb1e71f84ae3ffce945026de05` (git)
  - affected: `5.10.214 to before 5.10.252` (semver)
  - affected: `5.15.153 to before 5.15.202` (semver)
  - and 4 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.9`
  - unaffected: `before 6.9` (semver)
  - unaffected: `5.10.252 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.202 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.165 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.128 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.75 to 6.12.*, inclusive` (semver)
  - unaffected: `6.18.16 to 6.18.*, inclusive` (semver)
  - unaffected: `6.19.6 to 6.19.*, inclusive` (semver)
  - unaffected: `7.0 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Linux kernel versions affected by CVE-2026-43130 are listed by commit ranges and as 6.9 onward, with fixes in the stable 5.10, 5.15, 6.1 and 6.6 series and in mainline before 6.9. The Intel VT-d IOMMU driver can hard-lock the system when a PCIe device's link is down because of a fault and its ATS device-TLB invalidation is still sent during teardown. The source gives few details on how an attacker would trigger this. Upgrade to a fixed Linux kernel release for your branch; no workaround is listed.

Written 17 Nov 2026.

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0012, the 2nd percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 6 May 2026, 11:27 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-43130)
- 6 May 2026, 12:16 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-43130)

## Sources

- [CVE List: CVE-2026-43130](https://www.cve.org/CVERecord?id=CVE-2026-43130)
- [NVD: CVE-2026-43130](https://nvd.nist.gov/vuln/detail/CVE-2026-43130)

### References from the CNA

- <https://git.kernel.org/stable/c/581ce094d9eafb78ec4f9de77bd24b780c151236>
- <https://git.kernel.org/stable/c/e2c78c69f8faf2885ea4ceee08c71ac738f401a0>
- <https://git.kernel.org/stable/c/ead67d0378e90f419e385a43af29435242d80c12>
- <https://git.kernel.org/stable/c/01aed2f1d7cb8fdf4c60c5bb4727608cb82b401d>
- <https://git.kernel.org/stable/c/9813306610d0d718c863aaa70928bf57d7570ec0>
- <https://git.kernel.org/stable/c/9deaacc8dcaddb6ddc5b52e1e63b457450ec0f94>
- <https://git.kernel.org/stable/c/0da6697e577023d8867c7beb2d16a22510e4eea9>
- <https://git.kernel.org/stable/c/10e60d87813989e20eac1f3eda30b3bae461e7f9>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2026-43130>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2026-43130/>. Everything for agents: <https://agentprime.io/llms.txt>.
