linux-cve-announce - CVE-2025-23140: misc: pci_endpoint_test: Avoid issue of interrupts remaining after request

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: <2025050124-CVE-2025-23140-bd0d@gregkh>
Date: Thu,  1 May 2025 14:56:20 +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-23140: misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error

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

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

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

misc: pci_endpoint_test: Avoid issue of interrupts remaining after request_irq error

After devm_request_irq() fails with error in pci_endpoint_test_request_irq(),
the pci_endpoint_test_free_irq_vectors() is called assuming that all IRQs
have been released.

However, some requested IRQs remain unreleased, so there are still
/proc/irq/* entries remaining, and this results in WARN() with the
following message:

  remove_proc_entry: removing non-empty directory 'irq/30', leaking at least 'pci-endpoint-test.0'
  WARNING: CPU: 0 PID: 202 at fs/proc/generic.c:719 remove_proc_entry +0x190/0x19c

To solve this issue, set the number of remaining IRQs to test->num_irqs,
and release IRQs in advance by calling pci_endpoint_test_release_irq().

[kwilczynski: commit log]

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


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

	Issue introduced in 4.19 with commit e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and fixed in 6.1.135 with commit 9d5118b107b1a2353ed0dff24404aee2e6b7ca0a
	Issue introduced in 4.19 with commit e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and fixed in 6.6.88 with commit 5a4b7181213268c9b07bef8800905528435db44a
	Issue introduced in 4.19 with commit e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and fixed in 6.12.25 with commit 0557e70e2aeba8647bf5a950820b67cfb86533db
	Issue introduced in 4.19 with commit e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and fixed in 6.14.3 with commit 770407f6173f4f39f4e2c1b54422b79ce6c98bdb
	Issue introduced in 4.19 with commit e03327122e2c8e6ae4565ef5b3d3cbe4364546a1 and fixed in 6.15-rc1 with commit f6cb7828c8e17520d4f5afb416515d3fae1af9a9

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-23140
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/pci_endpoint_test.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/9d5118b107b1a2353ed0dff24404aee2e6b7ca0a
	https://git.kernel.org/stable/c/5a4b7181213268c9b07bef8800905528435db44a
	https://git.kernel.org/stable/c/0557e70e2aeba8647bf5a950820b67cfb86533db
	https://git.kernel.org/stable/c/770407f6173f4f39f4e2c1b54422b79ce6c98bdb
	https://git.kernel.org/stable/c/f6cb7828c8e17520d4f5afb416515d3fae1af9a9