iommu/tegra241-cmdqv: Require exactly one Stream ID for a vSID
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.527.2.67.3In the Linux kernel, the following vulnerability has been resolved:
iommu/tegra241-cmdqv: Require exactly one Stream ID for a vSID
tegra241_vintf_init_vsid() maps a guest vSID to a single physical Stream ID taken from master->streams[0], and only warns when the device does not have 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.
Reject the mapping with -EOPNOTSUPP if master->num_streams is not one.
From the CVE record · Linux
The Linux kernel’s tegra241-cmdqv code does not reject devices whose stream count is not exactly one when mapping a guest vSID. With multiple streams, guest vSID invalidation cannot reach entries for the other streams; with no streams, the code reads out of bounds. The input does not establish an attacker path, authentication requirements, or user-interaction requirements.
Engineers running Linux kernels that use tegra241-cmdqv should check their versions; affected versions are not specified.