linux-cve-announce - CVE-2025-40144: nvdimm: ndtest: Return -ENOMEM if devm_kcalloc() fails in ndtest

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: <2025111256-CVE-2025-40144-f4bd@gregkh>
Date: Wed, 12 Nov 2025 19:24:20 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40144: nvdimm: ndtest: Return -ENOMEM if devm_kcalloc() fails in ndtest_probe()

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

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

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

nvdimm: ndtest: Return -ENOMEM if devm_kcalloc() fails in ndtest_probe()

devm_kcalloc() may fail. ndtest_probe() allocates three DMA address
arrays (dcr_dma, label_dma, dimm_dma) and later unconditionally uses
them in ndtest_nvdimm_init(), which can lead to a NULL pointer
dereference under low-memory conditions.

Check all three allocations and return -ENOMEM if any allocation fails,
jumping to the common error path. Do not emit an extra error message
since the allocator already warns on allocation failure.

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


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

	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 5.15.195 with commit 972cbba5cd384bacdc2eb589776e1d0a9f42714f
	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 6.1.156 with commit bc8b56317ff83ef4bba89bda356b93978604694f
	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 6.6.112 with commit b808a3590c2884ca91316dbadbfcc1924f5893c7
	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 6.12.53 with commit e4a1e3e88160f7d7a2c33e3db8844073ed6eaf97
	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 6.17.3 with commit 8aea9d512c65eed0dad98b8d65ce74fe77c01b34
	Issue introduced in 5.11 with commit 9399ab61ad82154911563dd8635c585e3f24b16a and fixed in 6.18-rc1 with commit a9e6aa994917ee602798bbb03180a194b37865bb

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-40144
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:
	tools/testing/nvdimm/test/ndtest.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/972cbba5cd384bacdc2eb589776e1d0a9f42714f
	https://git.kernel.org/stable/c/bc8b56317ff83ef4bba89bda356b93978604694f
	https://git.kernel.org/stable/c/b808a3590c2884ca91316dbadbfcc1924f5893c7
	https://git.kernel.org/stable/c/e4a1e3e88160f7d7a2c33e3db8844073ed6eaf97
	https://git.kernel.org/stable/c/8aea9d512c65eed0dad98b8d65ce74fe77c01b34
	https://git.kernel.org/stable/c/a9e6aa994917ee602798bbb03180a194b37865bb