CVE-2025-21724: iommufd/iova_bitmap: Fix shift-out-of-bounds in iova_bitmap_offset_to_index()
In the Linux kernel, the following vulnerability has been resolved:
iommufd/iovabitmap: Fix shift-out-of-bounds in iovabitmapoffsettoindex()
Resolve a UBSAN shift-out-of-bounds issue in iovabitmapoffsettoindex() 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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.129-1 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.12.13-1 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.1.129 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.6.76 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.12.13 - Upgrade
Upgrade
linux/Kernelto a version that resolves this vulnerability.Fixed in 6.13.2 - Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 6.1.176-1Fixed in 6.1.190-1Fixed in 6.12.107-1Fixed in 6.12.115-2Fixed in 7.2.15-1
Event History
Frequently Asked Questions
What is the severity of CVE-2025-21724?
CVE-2025-21724 is classified as a medium severity vulnerability due to the potential for data corruption.
How do I fix CVE-2025-21724?
To resolve CVE-2025-21724, upgrade your Linux kernel to a patched version that addresses the issue.
What versions of the Linux kernel are affected by CVE-2025-21724?
CVE-2025-21724 affects Linux kernel versions between 6.1.0 to 6.1.129, 6.2.0 to 6.6.76, 6.7.0 to 6.12.13, and 6.13.0 to 6.13.2.
What impact does CVE-2025-21724 have on system security?
CVE-2025-21724 can lead to potential data integrity issues if exploited, making it a risk for systems using vulnerable kernel versions.
Is there a workaround for CVE-2025-21724?
There are currently no known workarounds for CVE-2025-21724, so updating the kernel is essential.