linux-cve-announce - CVE-2025-38006: net: mctp: Don't access ifa

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: <2025061841-CVE-2025-38006-5478@gregkh>
Date: Wed, 18 Jun 2025 11:28:40 +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-38006: net: mctp: Don't access ifa_index when missing

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

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

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

net: mctp: Don't access ifa_index when missing

In mctp_dump_addrinfo, ifa_index can be used to filter interfaces, but
only when the struct ifaddrmsg is provided. Otherwise it will be
comparing to uninitialised memory - reproducible in the syzkaller case from
dhcpd, or busybox "ip addr show".

The kernel MCTP implementation has always filtered by ifa_index, so
existing userspace programs expecting to dump MCTP addresses must
already be passing a valid ifa_index value (either 0 or a real index).

BUG: KMSAN: uninit-value in mctp_dump_addrinfo+0x208/0xac0 net/mctp/device.c:128
 mctp_dump_addrinfo+0x208/0xac0 net/mctp/device.c:128
 rtnl_dump_all+0x3ec/0x5b0 net/core/rtnetlink.c:4380
 rtnl_dumpit+0xd5/0x2f0 net/core/rtnetlink.c:6824
 netlink_dump+0x97b/0x1690 net/netlink/af_netlink.c:2309

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


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

	Issue introduced in 5.15 with commit 583be982d93479ea3d85091b0fd0b01201ede87d and fixed in 6.6.92 with commit acab78ae12c7fefb4f3bfe22e00770a5faa42724
	Issue introduced in 5.15 with commit 583be982d93479ea3d85091b0fd0b01201ede87d and fixed in 6.12.30 with commit d4d1561d17eb72908e4489c0900d96e0484fac20
	Issue introduced in 5.15 with commit 583be982d93479ea3d85091b0fd0b01201ede87d and fixed in 6.14.8 with commit 24fa213dffa470166ec014f979f36c6ff44afb45
	Issue introduced in 5.15 with commit 583be982d93479ea3d85091b0fd0b01201ede87d and fixed in 6.15 with commit f11cf946c0a92c560a890d68e4775723353599e1

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-38006
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:
	net/mctp/device.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/acab78ae12c7fefb4f3bfe22e00770a5faa42724
	https://git.kernel.org/stable/c/d4d1561d17eb72908e4489c0900d96e0484fac20
	https://git.kernel.org/stable/c/24fa213dffa470166ec014f979f36c6ff44afb45
	https://git.kernel.org/stable/c/f11cf946c0a92c560a890d68e4775723353599e1