Back to CVE records
Medium 5.5Published May 6, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects Linux and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
5.5 MEDIUM (v3.1, NVD)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
Not given
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
Linux
NVD analysis
Analyzed
Record last updated
May 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
Linux Linux
linux:linux (from the name)
from f873b85ec762c5a6abe94a7ddb31df5d3ba07d85 before 581ce094d9eafb78ec4f9de77bd24b780c151236; from d70f1c85113cd8c2aa8373f491ca5d1b22ec0554 before e2c78c69f8faf2885ea4ceee08c71ac738f401a0; from 34a7b30f56d30114bf4d436e4dc793afe326fbcf before ead67d0378e90f419e385a43af29435242d80c12; 2b74b2a92e524d7c8dec8e02e95ecf18b667c062 builds before 01aed2f1d7cb8fdf4c60c5bb4727608cb82b401d; from 4fc82cd907ac075648789cc3a00877778aa1838b before 9813306610d0d718c863aaa70928bf57d7570ec0; from 4fc82cd907ac075648789cc3a00877778aa1838b before 9deaacc8dcaddb6ddc5b52e1e63b457450ec0f94; 4fc82cd907ac075648789cc3a00877778aa1838b builds before 0da6697e577023d8867c7beb2d16a22510e4eea9; from 4fc82cd907ac075648789cc3a00877778aa1838b before 10e60d87813989e20eac1f3eda30b3bae461e7f9; and 8 more ranges
CNA record
linux linux_kernel
linux:linux_kernel
from 5.10.214 before 5.10.252; from 5.15.153 before 5.15.202; from 6.1.83 before 6.1.165; from 6.6.23 before 6.6.128; from 6.7.11 before 6.8; from 6.8.2 before 6.12.75; from 6.13 before 6.18.16; from 6.19 before 6.19.6
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.