linux-cve-announce - CVE-2025-21724: iommufd/iova_bitmap: Fix shift-out-of-bounds in iova_bitmap_offset_to

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025022647-CVE-2025-21724-f4b1@gregkh>
Date: Wed, 26 Feb 2025 18:06:19 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21724: iommufd/iova_bitmap: Fix shift-out-of-bounds in iova_bitmap_offset_to_index()

Description
===========

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.

The Linux kernel CVE team has assigned CVE-2025-21724 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 6.1 with commit 58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 and fixed in 6.1.129 with commit 44d9c94b7a3f29a3e07c4753603a35e9b28842a3
	Issue introduced in 6.1 with commit 58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 and fixed in 6.6.76 with commit 38ac76fc06bc6826a3e4b12a98efbe98432380a9
	Issue introduced in 6.1 with commit 58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 and fixed in 6.12.13 with commit d5d33f01b86af44b23eea61ee309e4ef22c0cdfe
	Issue introduced in 6.1 with commit 58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 and fixed in 6.13.2 with commit b1f8453b8ff1ab79a03820ef608256c499769cb6
	Issue introduced in 6.1 with commit 58ccf0190d19d9a8a41f8a02b9e06742b58df4a1 and fixed in 6.14-rc1 with commit e24c1551059268b37f6f40639883eafb281b8b9c

Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.

Unaffected versions might change over time as fixes are backported to
older supported kernel versions.  The official CVE entry at
	https://cve.org/CVERecord/?id=CVE-2025-21724
will be updated if fixes are backported, please check that for the most
up to date information about this issue.


Affected files
==============

The file(s) affected by this issue are:
	drivers/iommu/iommufd/iova_bitmap.c


Mitigation
==========

The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes.  Individual
changes are never tested alone, but rather are part of a larger kernel
release.  Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all.  If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
	https://git.kernel.org/stable/c/44d9c94b7a3f29a3e07c4753603a35e9b28842a3
	https://git.kernel.org/stable/c/38ac76fc06bc6826a3e4b12a98efbe98432380a9
	https://git.kernel.org/stable/c/d5d33f01b86af44b23eea61ee309e4ef22c0cdfe
	https://git.kernel.org/stable/c/b1f8453b8ff1ab79a03820ef608256c499769cb6
	https://git.kernel.org/stable/c/e24c1551059268b37f6f40639883eafb281b8b9c