linux-cve-announce - CVE-2025-37819: irqchip/gic-v2m: Prevent use after free of gicv2m_get

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: <2025050820-CVE-2025-37819-a3b9@gregkh>
Date: Thu,  8 May 2025 08:39:28 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-37819: irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()

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

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

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

irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode()

With ACPI in place, gicv2m_get_fwnode() is registered with the pci
subsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime
during a PCI host bridge probe. But, the call back is wrongly marked as
__init, causing it to be freed, while being registered with the PCI
subsystem and could trigger:

 Unable to handle kernel paging request at virtual address ffff8000816c0400
  gicv2m_get_fwnode+0x0/0x58 (P)
  pci_set_bus_msi_domain+0x74/0x88
  pci_register_host_bridge+0x194/0x548

This is easily reproducible on a Juno board with ACPI boot.

Retain the function for later use.

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


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

	Issue introduced in 4.5 with commit 0644b3daca28dcb320373ae20069c269c9386304 and fixed in 6.6.89 with commit 2f2803e4b5e4df2b08d378deaab78b1681ef9b30
	Issue introduced in 4.5 with commit 0644b3daca28dcb320373ae20069c269c9386304 and fixed in 6.12.26 with commit 3939d6f29d34cdb60e3f68b76e39e00a964a1d51
	Issue introduced in 4.5 with commit 0644b3daca28dcb320373ae20069c269c9386304 and fixed in 6.14.5 with commit 47bee0081b483b077c7560bc5358ad101f89c8ef
	Issue introduced in 4.5 with commit 0644b3daca28dcb320373ae20069c269c9386304 and fixed in 6.15-rc4 with commit 3318dc299b072a0511d6dfd8367f3304fb6d9827

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-37819
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/irqchip/irq-gic-v2m.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/2f2803e4b5e4df2b08d378deaab78b1681ef9b30
	https://git.kernel.org/stable/c/3939d6f29d34cdb60e3f68b76e39e00a964a1d51
	https://git.kernel.org/stable/c/47bee0081b483b077c7560bc5358ad101f89c8ef
	https://git.kernel.org/stable/c/3318dc299b072a0511d6dfd8367f3304fb6d9827