linux-cve-announce - CVE-2025-21770: iommu: Fix potential memory leak in iopf_queue_remove

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: <2025022606-CVE-2025-21770-d7e0@gregkh>
Date: Wed, 26 Feb 2025 18:17:26 -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-21770: iommu: Fix potential memory leak in iopf_queue_remove_device()

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

In the Linux kernel, the following vulnerability has been resolved:

iommu: Fix potential memory leak in iopf_queue_remove_device()

The iopf_queue_remove_device() helper removes a device from the per-iommu
iopf queue when PRI is disabled on the device. It responds to all
outstanding iopf's with an IOMMU_PAGE_RESP_INVALID code and detaches the
device from the queue.

However, it fails to release the group structure that represents a group
of iopf's awaiting for a response after responding to the hardware. This
can cause a memory leak if iopf_queue_remove_device() is called with
pending iopf's.

Fix it by calling iopf_free_group() after the iopf group is responded.

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


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

	Issue introduced in 6.9 with commit 19911232713573a2ebea84a25bd4d71d024ed86b and fixed in 6.12.16 with commit db60d2d896a17decd58d143eef92cf22eb0a0176
	Issue introduced in 6.9 with commit 19911232713573a2ebea84a25bd4d71d024ed86b and fixed in 6.13.4 with commit 90d5429cd2921ca2714684ed525898d431bb9283
	Issue introduced in 6.9 with commit 19911232713573a2ebea84a25bd4d71d024ed86b and fixed in 6.14-rc3 with commit 9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08

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-21770
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/io-pgfault.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/db60d2d896a17decd58d143eef92cf22eb0a0176
	https://git.kernel.org/stable/c/90d5429cd2921ca2714684ed525898d431bb9283
	https://git.kernel.org/stable/c/9759ae2cee7cd42b95f1c48aa3749bd02b5ddb08