linux-cve-announce - CVE-2025-21742: usbnet: ipheth: use static NDP16 location in URB

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: <2025022600-CVE-2025-21742-7d50@gregkh>
Date: Wed, 26 Feb 2025 18:11:24 -0800
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-21742: usbnet: ipheth: use static NDP16 location in URB

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

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

usbnet: ipheth: use static NDP16 location in URB

Original code allowed for the start of NDP16 to be anywhere within the
URB based on the `wNdpIndex` value in NTH16. Only the start position of
NDP16 was checked, so it was possible for even the fixed-length part
of NDP16 to extend past the end of URB, leading to an out-of-bounds
read.

On iOS devices, the NDP16 header always directly follows NTH16. Rely on
and check for this specific format.

This, along with NCM-specific minimal URB length check that already
exists, will ensure that the fixed-length part of NDP16 plus a set
amount of DPEs fit within the URB.

Note that this commit alone does not fully address the OoB read.
The limit on the amount of DPEs needs to be enforced separately.

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


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

	Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.6.78 with commit 8fb062178e1ce180e2cfdc9abc83a1b9fea381ca
	Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.12.14 with commit cf1ac7f7cf601ac31d1580559c002b5e37b733b7
	Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.13.3 with commit 2b619445dcb6dab97d8ed033fb57225aca1288c4
	Issue introduced in 6.5 with commit a2d274c62e44b1995c170595db3865c6fe701226 and fixed in 6.14-rc1 with commit 86586dcb75cb8fd062a518aca8ee667938b91efb

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-21742
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/net/usb/ipheth.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/8fb062178e1ce180e2cfdc9abc83a1b9fea381ca
	https://git.kernel.org/stable/c/cf1ac7f7cf601ac31d1580559c002b5e37b733b7
	https://git.kernel.org/stable/c/2b619445dcb6dab97d8ed033fb57225aca1288c4
	https://git.kernel.org/stable/c/86586dcb75cb8fd062a518aca8ee667938b91efb