iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.447.1.87.2In 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.
From the CVE record · Linux
The Linux kernel's arm-smmu-v3-iommufd code assumes a vDEVICE has exactly one Stream ID. With multiple streams, a guest vSID invalidation misses entries for the other streams; with no streams, the code reads out of bounds. The input does not specify attacker access requirements or user interaction.
Engineers running Linux kernels with arm-smmu-v3-iommufd should check whether their kernel is affected; no affected versions are specified.