linux-cve-announce - CVE-2022-50482: iommu/vt-d: Clean up si_domain in the init

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: <2025100440-CVE-2022-50482-0291@gregkh>
Date: Sat,  4 Oct 2025 17:16:41 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2022-50482: iommu/vt-d: Clean up si_domain in the init_dmars() error path

From: Greg Kroah-Hartman <gregkh@...nel.org>

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

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

iommu/vt-d: Clean up si_domain in the init_dmars() error path

A splat from kmem_cache_destroy() was seen with a kernel prior to
commit ee2653bbe89d ("iommu/vt-d: Remove domain and devinfo mempool")
when there was a failure in init_dmars(), because the iommu_domain
cache still had objects. While the mempool code is now gone, there
still is a leak of the si_domain memory if init_dmars() fails. So
clean up si_domain in the init_dmars() error path.

The Linux kernel CVE team has assigned CVE-2022-50482 to this issue.


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

	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 4.14.298 with commit 749bea542b67513e99240dc58bbfc099e842d508
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 4.19.264 with commit 5cecfe151874b835331efe086bbdcaeaf64f6b90
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 5.4.221 with commit 724483b585a1b1e063d42ac5aa835707ff2ec165
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 5.10.152 with commit d74196bb278b8f8af88e16bd595997dfa3d6fdb0
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 5.15.76 with commit 0365d6af75f9f2696e94a0fef24a2c8464c037c8
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 6.0.6 with commit c4ad3ae4c6be9d8b0701761c839771116bca6ea3
	Issue introduced in 4.2 with commit 86080ccc223aabf8d0b85a504f4f06aa88e82fb3 and fixed in 6.1 with commit 620bf9f981365c18cc2766c53d92bf8131c63f32

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-2022-50482
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/intel/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/749bea542b67513e99240dc58bbfc099e842d508
	https://git.kernel.org/stable/c/5cecfe151874b835331efe086bbdcaeaf64f6b90
	https://git.kernel.org/stable/c/724483b585a1b1e063d42ac5aa835707ff2ec165
	https://git.kernel.org/stable/c/d74196bb278b8f8af88e16bd595997dfa3d6fdb0
	https://git.kernel.org/stable/c/0365d6af75f9f2696e94a0fef24a2c8464c037c8
	https://git.kernel.org/stable/c/c4ad3ae4c6be9d8b0701761c839771116bca6ea3
	https://git.kernel.org/stable/c/620bf9f981365c18cc2766c53d92bf8131c63f32