linux-cve-announce - CVE-2025-37815: misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration

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: <2025050818-CVE-2025-37815-7882@gregkh>
Date: Thu,  8 May 2025 08:39:24 +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-37815: misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration

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

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

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

misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration

Resolve kernel panic while accessing IRQ handler associated with the
generated IRQ. This is done by acquiring the spinlock and storing the
current interrupt state before handling the interrupt request using
generic_handle_irq.

A previous fix patch was submitted where 'generic_handle_irq' was
replaced with 'handle_nested_irq'. However, this change also causes
the kernel panic where after determining which GPIO triggered the
interrupt and attempting to call handle_nested_irq with the mapped
IRQ number, leads to a failure in locating the registered handler.

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


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

	Issue introduced in 6.1.125 with commit 79aef6187e16b2d32307c8ff610e9e04f7f86e1f and fixed in 6.1.136 with commit 1263d5f581908602c618c6665e683c4436383a09
	Issue introduced in 6.6.72 with commit 25692750c0259c5b65afec467d97201a485e8a00 and fixed in 6.6.89 with commit 62957f58ab3aa7fa792dc6ff3575624062539a4d
	Issue introduced in 6.12.10 with commit 47d3749ec0cb56b7b98917c190a8c10cb54216fd and fixed in 6.12.26 with commit 12cc2193f2b9548e8ea5fbce8201b44158222edf
	Issue introduced in 6.13 with commit 194f9f94a5169547d682e9bbcc5ae6d18a564735 and fixed in 6.14.5 with commit 4e02059dc91068bc5017b8546f9ec3b930f6d6a6
	Issue introduced in 6.13 with commit 194f9f94a5169547d682e9bbcc5ae6d18a564735 and fixed in 6.15-rc4 with commit 18eb77c75ed01439f96ae5c0f33461eb5134b907

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-37815
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/misc/mchp_pci1xxxx/mchp_pci1xxxx_gpio.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/1263d5f581908602c618c6665e683c4436383a09
	https://git.kernel.org/stable/c/62957f58ab3aa7fa792dc6ff3575624062539a4d
	https://git.kernel.org/stable/c/12cc2193f2b9548e8ea5fbce8201b44158222edf
	https://git.kernel.org/stable/c/4e02059dc91068bc5017b8546f9ec3b930f6d6a6
	https://git.kernel.org/stable/c/18eb77c75ed01439f96ae5c0f33461eb5134b907