linux-cve-announce - CVE-2024-53232: iommu/s390: Implement blocking domain

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: <2024122737-CVE-2024-53232-6919@gregkh>
Date: Fri, 27 Dec 2024 14:53:18 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-53232: iommu/s390: Implement blocking domain

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

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

iommu/s390: Implement blocking domain

This fixes a crash when surprise hot-unplugging a PCI device. This crash
happens because during hot-unplug __iommu_group_set_domain_nofail()
attaching the default domain fails when the platform no longer
recognizes the device as it has already been removed and we end up with
a NULL domain pointer and UAF. This is exactly the case referred to in
the second comment in __iommu_device_set_domain() and just as stated
there if we can instead attach the blocking domain the UAF is prevented
as this can handle the already removed device. Implement the blocking
domain to use this handling.  With this change, the crash is fixed but
we still hit a warning attempting to change DMA ownership on a blocked
device.

The Linux kernel CVE team has assigned CVE-2024-53232 to this issue.

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

	Issue introduced in 6.7 with commit c76c067e488ccd55734c3e750799caf2c5956db6 and fixed in 6.11.11 with commit 3be34fa1cdbf180c1a948cfededfdf2cdc497199
	Issue introduced in 6.7 with commit c76c067e488ccd55734c3e750799caf2c5956db6 and fixed in 6.12.2 with commit bd89d94f3ea6fdaee983cbc69226a00b9bde6d59
	Issue introduced in 6.7 with commit c76c067e488ccd55734c3e750799caf2c5956db6 and fixed in 6.13-rc1 with commit ecda483339a5151e3ca30d6b82691ef6f1d17912

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-2024-53232
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:
	arch/s390/include/asm/pci.h
	arch/s390/pci/pci.c
	arch/s390/pci/pci_debug.c
	drivers/iommu/s390-iommu.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/3be34fa1cdbf180c1a948cfededfdf2cdc497199
	https://git.kernel.org/stable/c/bd89d94f3ea6fdaee983cbc69226a00b9bde6d59
	https://git.kernel.org/stable/c/ecda483339a5151e3ca30d6b82691ef6f1d17912