CVE-2026-43161— Linux kernel 安全漏洞
一分钟漏洞结论
影响对象
Linux Linux
利用判断
尚无明确在野利用证据，仍需结合暴露面评估
建议动作
优先检查厂商安全公告和参考链接中的修复版本；无法立即升级时，限制受影响服务暴露并加强监测。
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于在非可扩展模式下对不可访问的PCIe设备跳过dev-iotlb刷新，可能导致系统硬锁定。
影响版本矩阵 14
| 厂商 | 产品 | 版本范围 | 状态 |
|---|---|---|---|
| Linux | Linux | 37764b952e1b39053defc7ebe5dcd8c4e3e78de9< 48b3f08e68b29a79527869cdde7298ca2a9b9646 |
affected |
37764b952e1b39053defc7ebe5dcd8c4e3e78de9< e70d5feb10c5ba2bbf7ca400b8f39a2f82d653e8 |
affected | ||
37764b952e1b39053defc7ebe5dcd8c4e3e78de9< bc0490ad9edf5c6f98e39fbbee2877b85261a5ae |
affected | ||
37764b952e1b39053defc7ebe5dcd8c4e3e78de9< 42662d19839f34735b718129ea200e3734b07e50 |
affected | ||
99301a53a1378f8863ac7850b9589f997bb0e125 |
affected | ||
948ec6d003280d49aca49b366aa5cb140f87434d |
affected | ||
5.12.19< 5.13 |
affected | ||
5.13.4< 5.14 |
affected | ||
| … +6 条更多 | |||
获取后续新漏洞提醒
登录后订阅
一、 漏洞 CVE-2026-43161 基础信息
漏洞信息
对漏洞内容有疑问？看看神龙的深度分析是否有帮助！
查看神龙十问 ↗
尽管我们使用了先进的大模型技术，但其输出仍可能包含不准确或过时的信息。神龙努力确保数据的准确性，但请您根据实际情况进行核实和判断。
Vulnerability Title
iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode
来源: CVE Program / CVE List V5
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved:
iommu/vt-d: Skip dev-iotlb flush for inaccessible PCIe device without scalable mode
PCIe endpoints with ATS enabled and passed through to userspace
(e.g., QEMU, DPDK) can hard-lock the host when their link drops,
either by surprise removal or by a link fault.
Commit 4fc82cd907ac ("iommu/vt-d: Don't issue ATS Invalidation
request when device is disconnected") adds pci_dev_is_disconnected()
to devtlb_invalidation_with_pasid() so ATS invalidation is skipped
only when the device is being safely removed, but it applies only
when Intel IOMMU scalable mode is enabled.
With scalable mode disabled or unsupported, a system hard-lock
occurs when a PCIe endpoint's link drops because the Intel IOMMU
waits indefinitely for an ATS invalidation that cannot complete.
Call Trace:
qi_submit_sync
qi_flush_dev_iotlb
__context_flush_dev_iotlb.part.0
domain_context_clear_one_cb
pci_for_each_dma_alias
device_block_translation
blocking_domain_attach_dev
iommu_deinit_device
__iommu_group_remove_device
iommu_release_device
iommu_bus_notifier
blocking_notifier_call_chain
bus_notify
device_del
pci_remove_bus_device
pci_stop_and_remove_bus_device
pciehp_unconfigure_device
pciehp_disable_slot
pciehp_handle_presence_or_link_change
pciehp_ist
Commit 81e921fd3216 ("iommu/vt-d: Fix NULL domain on device release")
adds intel_pasid_teardown_sm_context() to intel_iommu_release_device(),
which calls qi_flush_dev_iotlb() and can also hard-lock the system
when a PCIe endpoint's link drops.
Call Trace:
qi_submit_sync
qi_flush_dev_iotlb
__context_flush_dev_iotlb.part.0
intel_context_flush_no_pasid
device_pasid_table_teardown
pci_pasid_table_teardown
pci_for_each_dma_alias
intel_pasid_teardown_sm_context
intel_iommu_release_device
iommu_deinit_device
__iommu_group_remove_device
iommu_release_device
iommu_bus_notifier
blocking_notifier_call_chain
bus_notify
device_del
pci_remove_bus_device
pci_stop_and_remove_bus_device
pciehp_unconfigure_device
pciehp_disable_slot
pciehp_handle_presence_or_link_change
pciehp_ist
Sometimes the endpoint loses connection without a link-down event
(e.g., due to a link fault); killing the process (virsh destroy)
then hard-locks the host.
Call Trace:
qi_submit_sync
qi_flush_dev_iotlb
__context_flush_dev_iotlb.part.0
domain_context_clear_one_cb
pci_for_each_dma_alias
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
pci_dev_is_disconnected() only covers safe-removal paths;
pci_device_is_present() tests accessibility by reading
vendor/device IDs and internally calls pci_dev_is_disconnected().
On a ConnectX-5 (8 GT/s, x2) this costs ~70 µs.
Since __context_flush_dev_iotlb() is only called on
{attach,release}_dev paths (not hot), add pci_device_is_present()
there to skip inaccessible devices and avoid the hard-lock.
来源: CVE Program / CVE List V5
CVSS Information
N/A
来源: CVE Program / CVE List V5
Vulnerability Type
N/A
来源: CVE Program / CVE List V5
Vulnerability Title
Linux kernel 安全漏洞
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞，该漏洞源于在非可扩展模式下对不可访问的PCIe设备跳过dev-iotlb刷新，可能导致系统硬锁定。
来源: 中国国家信息安全漏洞库 CNNVD
CVSS Information
N/A
来源: 中国国家信息安全漏洞库 CNNVD
Vulnerability Type
N/A
来源: 中国国家信息安全漏洞库 CNNVD
受影响产品
二、漏洞 CVE-2026-43161 的公开POC
| # | POC 描述 | 源链接 | 神龙链接 |
|---|
AI 生成 POC
高级
未找到公开 POC。
登录以生成 AI POC三、漏洞 CVE-2026-43161 的情报信息
请登录查看更多情报信息。
CVE-2026-43161 补丁与修复 (4)
同批安全公告 · Linux · 2026-05-06 · 共 224 条
| CVE-2026-43208 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43125 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43198 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43186 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43185 | 9.8 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43114 | 9.4 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43197 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43117 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43083 | 9.1 CRITICAL | Linux kernel 安全漏洞 |
| CVE-2026-43239 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43113 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43158 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43232 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43172 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43283 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43176 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43112 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43215 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43249 | 8.8 HIGH | Linux kernel 安全漏洞 |
| CVE-2026-43110 | 8.8 HIGH | Linux kernel 安全漏洞 |
显示前 20 条，共 224 条。 查看全部 → →
IV. Related Vulnerabilities
V. Comments for CVE-2026-43161
暂无评论