iommu: Fix potential memory leak in iopf_queue_remove_device()
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 90d5429cd2921ca2714684ed525898d431bb9283, Kernel 9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08 and Kernel db60d2d896a17decd58d143eef92cf22eb0a0176.
In the Linux kernel, the following vulnerability has been resolved: iommu: Fix potential memory leak in iopf_queue_remove_device() The iopf_queue_remove_device() helper removes a device from the per-iommu iopf queue when PRI is disabled on the device. It responds to all outstanding iopf's with an IOMMU_PAGE_RESP_INVALID code and detaches the device from the queue. However, it fails to release the group structure that represents a group of iopf's awaiting for a response after responding to the hardware. This can cause a memory leak if iopf_queue_remove_device() is called with pending iopf's. Fix it by calling iopf_free_group() after the iopf group is responded.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | =6.9, >=19911232713573a2ebea84a25bd4d71d024ed86b <90d5429cd2921ca2714684ed525898d431bb9283, >=19911232713573a2ebea84a25bd4d71d024ed86b <9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08, >=19911232713573a2ebea84a25bd4d71d024ed86b <db60d2d896a17decd58d143eef92cf22eb0a0176 | 90d5429cd2921ca2714684ed525898d431bb9283, 9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08, db60d2d896a17decd58d143eef92cf22eb0a0176 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket