iommufd/iova_bitmap: Fix shift-out-of-bounds in iova_bitmap_offset_to_index()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
iommufd/iova_bitmap: Fix shift-out-of-bounds in iova_bitmap_offset_to_index()
Resolve a UBSAN shift-out-of-bounds issue in iova_bitmap_offset_to_index() where shifting the constant "1" (of type int) by bitmap->mapped.pgshift (an unsigned long value) could result in undefined behavior.
The constant "1" defaults to a 32-bit "int", and when "pgshift" exceeds 31 (e.g., pgshift = 63) the shift operation overflows, as the result cannot be represented in a 32-bit type.
To resolve this, the constant is updated to "1UL", promoting it to an unsigned long type to match the operand's type.
From the CVE record · Linux
The Linux kernel's iova_bitmap_offset_to_index() can perform an out-of-bounds shift when pgshift exceeds 31, causing undefined behavior. The input does not establish what an attacker could do or whether exploitation requires local access, authentication, or user interaction.
Engineers running Linux kernels with the affected iommufd/iova_bitmap code should check their versions; affected versions are not specified.