linux-cve-announce - CVE-2025-40053: net: dlink: handle copy

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: <2025102814-CVE-2025-40053-8e42@gregkh>
Date: Tue, 28 Oct 2025 12:48:30 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2025-40053: net: dlink: handle copy_thresh allocation failure

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

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

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

net: dlink: handle copy_thresh allocation failure

The driver did not handle failure of `netdev_alloc_skb_ip_align()`.
If the allocation failed, dereferencing `skb->protocol` could lead to
a NULL pointer dereference.

This patch tries to allocate `skb`. If the allocation fails, it falls
back to the normal path.

Tested-on: D-Link DGE-550T Rev-A3

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


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

	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 5.15.195 with commit 5aa9b885602811a026a3f45c92ea2b4b04c54f09
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.1.156 with commit 9d49e4b14609e1a20d931e718962c4b6b5485174
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.6.112 with commit ea87151df398d407a632c7bf63013290f01c5009
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.12.53 with commit 7ed5010fef0930f4322d620052edc854ef3ec41f
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.17.3 with commit fd7b6b2c920d7fd370a612be416a904d6e1ebe55
	Issue introduced in 2.6.12 with commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 and fixed in 6.18-rc1 with commit 8169a6011c5fecc6cb1c3654c541c567d3318de8

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-40053
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/ethernet/dlink/dl2k.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/5aa9b885602811a026a3f45c92ea2b4b04c54f09
	https://git.kernel.org/stable/c/9d49e4b14609e1a20d931e718962c4b6b5485174
	https://git.kernel.org/stable/c/ea87151df398d407a632c7bf63013290f01c5009
	https://git.kernel.org/stable/c/7ed5010fef0930f4322d620052edc854ef3ec41f
	https://git.kernel.org/stable/c/fd7b6b2c920d7fd370a612be416a904d6e1ebe55
	https://git.kernel.org/stable/c/8169a6011c5fecc6cb1c3654c541c567d3318de8