iommu/arm-smmu-v3-iommufd: Require exactly one Stream ID for a vDEVICE
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.44, 7.1.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From d68beb276ba26cec47350a6d468e967673ee0c56 · fixed in 3808bab5d95ae79e333e11f6a73d178e084c645d; From d68beb276ba26cec47350a6d468e967673ee0c56 · fixed in 0acbc621341aca4eb94d9c2f43e1ab273ff088f0; From d68beb276ba26cec47350a6d468e967673ee0c56 · fixed in c3b8ee84a965058b41275069d4696f37a8b14bf6
- Linux Linux
6.13
- KernelLinux
From 6.13.0 · fixed in 6.18.44; From 6.19.0 · fixed in 7.1.8