iommupt: Fix short gather if the unmap goes into a large mapping
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommupt: Fix short gather if the unmap goes into a large mapping
unmap has the odd behavior that it can unmap more than requested if the ending point lands within the middle of a large or contiguous IOPTE.
In this case the gather should flush everything unmapped which can be larger than what was requested to be unmapped. The gather was only flushing the range requested to be unmapped, not extending to the extra range, resulting in a short invalidation if the caller hits this special condition.
This was found by the new invalidation/gather test I am adding in preparation for ARMv8. Claude deduced the root cause.
As far as I remember nothing relies on unmapping a large entry, so this is likely not a triggerable bug.
From the CVE record · Linux
The iommupt unmap operation can unmap more than requested when the requested end falls inside a large or contiguous IOPTE, but its gather operation may not invalidate the entire unmapped range. The report says this is likely not triggerable; it does not identify an attacker action or specify network, authentication, or user-interaction conditions.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.