همهٔ گزارش‌ها
زیاد

kernel: iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE

متن اصلی

نسخه‌های متأثر

نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده
نسخه‌های متأثر
نامشخص
نسخهٔ اصلاح‌شده
اعلام نشده

بهره‌برداری

CVE-2026-74573

احتمال بهره‌برداری در ۳۰ روز آینده: 0.13%

FIRST EPSS · ۱۴۰۵/۰۸/۲۹

شرح آسیب‌پذیری

In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE arm_vsmmu_vsid_to_sid() maps a guest's vSID to a single physical Stream ID taken from master->streams[0], assuming a device has exactly one stream. A device with several streams gets only its first one mapped, so a guest vSID invalidation cannot reach the others' ATC and IOTLB entries; a device with none makes master->streams a ZERO_SIZE_PTR, read out of bounds. Add an arm_vsmmu_vdevice_init() op to reject the vDEVICE with -EOPNOTSUPP when master->num_streams is not one, rather than mapping it silently.

A flaw was found in the Linux kernel's ARM System Memory Management Unit version 3 (SMMUv3) IOMMU driver. This vulnerability occurs because the driver incorrectly assumes that a virtual device (vDEVICE) has only one Stream ID. This can lead to a guest operating system's virtual Stream ID invalidation failing to clear all relevant entries, potentially resulting in information disclosure or data integrity issues. Additionally, if a virtual device has no streams, an out-of-bounds read can occur, which may lead to a denial of service.