CVE-2025-40053
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
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A null pointer dereference in the Linux kernel D-Link driver (dlink) due to unhandled skb allocation failure in copy_thresh path.
Vulnerability
Description
CVE-2025-40053 is a NULL pointer dereference vulnerability in the Linux kernel's D-Link (dlink) network driver. The driver calls netdev_alloc_skb_ip_align() to allocate a socket buffer (skb) but does not check whether the allocation succeeds. If the allocation fails, the code proceeds to dereference skb->protocol, leading to a NULL pointer dereference and a kernel crash [1][2][3].
Exploitation
An attacker with local access or the ability to trigger network activity on a D-Link DGE-550T (Rev-A3) interface could cause memory pressure conditions that make the SKB allocation fail. Because the driver lacks a proper error-handling path, subsequent access to the SKB's protocol field results in a NULL pointer dereference. No prior authentication is required to trigger the vulnerable code path when network traffic is processed [1][2][3].
Impact
Successful exploitation results in a denial-of-service (DoS) condition through a kernel crash. The issue may also be exploitable for privilege escalation or other arbitrary effects if an attacker can control the state of the allocation failure and the subsequent crash, though the primary impact is system availability loss [1][2][3].
Mitigation
The Linux kernel maintainers have fixed the issue by adding a fallback path when the SKB allocation fails, ensuring the driver does not dereference a NULL pointer. Users should apply the stable kernel updates containing the fix. No workaround is no workaround; the vulnerability is patched, and affected systems should update to the latest kernel version [1][2][3].
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
784fd710a704f5aa9b88560289d49e4b14609ea87151df3987ed5010fef09fd7b6b2c920d8169a6011c5fVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
7- git.kernel.org/stable/c/5aa9b885602811a026a3f45c92ea2b4b04c54f09nvd
- git.kernel.org/stable/c/7ed5010fef0930f4322d620052edc854ef3ec41fnvd
- git.kernel.org/stable/c/8169a6011c5fecc6cb1c3654c541c567d3318de8nvd
- git.kernel.org/stable/c/84fd710a704f3d53d4120e452e86cea558cf73a8nvd
- git.kernel.org/stable/c/9d49e4b14609e1a20d931e718962c4b6b5485174nvd
- git.kernel.org/stable/c/ea87151df398d407a632c7bf63013290f01c5009nvd
- git.kernel.org/stable/c/fd7b6b2c920d7fd370a612be416a904d6e1ebe55nvd
News mentions
0No linked articles in our index yet.