linux-cve-announce - CVE-2025-38444: raid10: cleanup memleak at raid10_make

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: <2025072503-CVE-2025-38444-4b60@gregkh>
Date: Fri, 25 Jul 2025 17:28:06 +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-38444: raid10: cleanup memleak at raid10_make_request

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

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

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

raid10: cleanup memleak at raid10_make_request

If raid10_read_request or raid10_write_request registers a new
request and the REQ_NOWAIT flag is set, the code does not
free the malloc from the mempool.

unreferenced object 0xffff8884802c3200 (size 192):
   comm "fio", pid 9197, jiffies 4298078271
   hex dump (first 32 bytes):
     00 00 00 00 00 00 00 00 88 41 02 00 00 00 00 00  .........A......
     08 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
   backtrace (crc c1a049a2):
     __kmalloc+0x2bb/0x450
     mempool_alloc+0x11b/0x320
     raid10_make_request+0x19e/0x650 [raid10]
     md_handle_request+0x3b3/0x9e0
     __submit_bio+0x394/0x560
     __submit_bio_noacct+0x145/0x530
     submit_bio_noacct_nocheck+0x682/0x830
     __blkdev_direct_IO_async+0x4dc/0x6b0
     blkdev_read_iter+0x1e5/0x3b0
     __io_read+0x230/0x1110
     io_read+0x13/0x30
     io_issue_sqe+0x134/0x1180
     io_submit_sqes+0x48c/0xe90
     __do_sys_io_uring_enter+0x574/0x8b0
     do_syscall_64+0x5c/0xe0
     entry_SYSCALL_64_after_hwframe+0x76/0x7e

V4: changing backing tree to see if CKI tests will pass.
The patch code has not changed between any versions.

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


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

	Issue introduced in 5.15.111 with commit 39db562b3fedb93978a7e42dd216b306740959f8 and fixed in 5.15.189 with commit 10c6021a609deb95f23f0cc2f89aa9d4bffb14c7
	Issue introduced in 5.17 with commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and fixed in 6.1.146 with commit 9af149ca9d0dab6e59e813519d309eff62499864
	Issue introduced in 5.17 with commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and fixed in 6.6.99 with commit 8fc3d7b23d139e3cbc944c15d99b3cdbed797d2d
	Issue introduced in 5.17 with commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and fixed in 6.12.39 with commit 2941155d9a5ae098b480d551f3a5f8605d4f9af5
	Issue introduced in 5.17 with commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and fixed in 6.15.7 with commit ed7bcd9f617e4107ac0813c516e72e6b8f6029bd
	Issue introduced in 5.17 with commit c9aa889b035fca4598ae985a0f0c76ebbb547ad2 and fixed in 6.16-rc6 with commit 43806c3d5b9bb7d74ba4e33a6a8a41ac988bde24

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-38444
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/md/raid10.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/10c6021a609deb95f23f0cc2f89aa9d4bffb14c7
	https://git.kernel.org/stable/c/9af149ca9d0dab6e59e813519d309eff62499864
	https://git.kernel.org/stable/c/8fc3d7b23d139e3cbc944c15d99b3cdbed797d2d
	https://git.kernel.org/stable/c/2941155d9a5ae098b480d551f3a5f8605d4f9af5
	https://git.kernel.org/stable/c/ed7bcd9f617e4107ac0813c516e72e6b8f6029bd
	https://git.kernel.org/stable/c/43806c3d5b9bb7d74ba4e33a6a8a41ac988bde24