CVE-2026-89445
CVE CVE-2026-89445EUVD EUVD-2026-76351Published 2026-09-11T19:43:12.000ZLast changed 2026-09-13T06:29:27.000ZCVSS 8.8
What the advisory describes
In the Linux kernel, the following vulnerability has been resolved: iommufd: Fix UAF in selftest IOPF reporting IOMMUFD selftest TRIGGER_IOPF borrows an attach handle from group->pasid_array without synchronizing against PASID detach, then a concurrent iommu_report_device_fault() can dereference that borrowed handle's domain pointer after the detach erases the handle and frees the backing struct iommufd_attach_handle. TRIGGER_IOPF then dereferences the freed handle, causing a UAF. Fix by adding a iopf_rwsem in mock_dev to follow the expected design of a real driver. Hold its read side across the whole iommu_report_device_fault() call, and its write side around every path that attaches, detaches, or replaces a device domain. This can block new reports and drains in-flight reports before an old attach handle or the IOPF fault parameter can be removed. Also take the write side while registering a mock device, since it can invoke the mock driver's default-domain attach callback.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux ddee19971081b42615d62f4fdada21274708ed4d <cab2895729516799384d48560e6fca105fb3f927; patch: 0; 6.11; ddee19971081b42615d62f4fdada21274708ed4d <8c07df7cdfcf52f1ff276c588612aabc6c6b8399; ddee19971081b42615d62f4fdada21274708ed4d <e27e90bde68b2ab92e63ed19caad1ef57188bea0; patch: 7.3-rc1; patch: 6.18.50; patch: 7.2.4
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.