iommufd: Do not add the same hwpt to the ioas->hwpt_list twice
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel b4ff830eca097df51af10a9be29e8cc817327919 and Kernel c44adefdcf472f946f0632f4e0ddcbf3e00b8516.
In the Linux kernel, the following vulnerability has been resolved: iommufd: Do not add the same hwpt to the ioas->hwpt_list twice The hwpt is added to the hwpt_list only during its creation, it is never added again. This hunk is some missed leftover from rework. Adding it twice will corrupt the linked list in some cases. It effects HWPT specific attachment, which is something the test suite cannot cover until we can create a legitimate struct device with a non-system iommu "driver" (ie we need the bus removed from the iommu code)
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.2, >=e8d57210035b6377d424ba964961892d01127cf6 <b4ff830eca097df51af10a9be29e8cc817327919, >=e8d57210035b6377d424ba964961892d01127cf6 <c44adefdcf472f946f0632f4e0ddcbf3e00b8516 | b4ff830eca097df51af10a9be29e8cc817327919, c44adefdcf472f946f0632f4e0ddcbf3e00b8516 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket