CVE-2025-39987
Description
In the Linux kernel, the following vulnerability has been resolved:
can: hi311x: populate ndo_change_mtu() to prevent buffer overflow
Sending an PF_PACKET allows to bypass the CAN framework logic and to directly reach the xmit() function of a CAN driver. The only check which is performed by the PF_PACKET framework is to make sure that skb->len fits the interface's MTU.
Unfortunately, because the sun4i_can driver does not populate its net_device_ops->ndo_change_mtu(), it is possible for an attacker to configure an invalid MTU by doing, for example:
$ ip link set can0 mtu 9999
After doing so, the attacker could open a PF_PACKET socket using the ETH_P_CANXL protocol:
socket(PF_PACKET, SOCK_RAW, htons(ETH_P_CANXL))
to inject a malicious CAN XL frames. For example:
struct canxl_frame frame = { .flags = 0xff, .len = 2048, };
The CAN drivers' xmit() function are calling can_dev_dropped_skb() to check that the skb is valid, unfortunately under above conditions, the malicious packet is able to go through can_dev_dropped_skb() checks:
1. the skb->protocol is set to ETH_P_CANXL which is valid (the function does not check the actual device capabilities).
- the length is a valid CAN XL length.
And so, hi3110_hard_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN frame. The driver will consume frame->len as-is with no further checks.
This can result in a buffer overflow later on in hi3110_hw_tx() on this line:
memcpy(buf + HI3110_FIFO_EXT_DATA_OFF, frame->data, frame->len);
Here, frame->len corresponds to the flags field of the CAN XL frame. In our previous example, we set canxl_frame->flags to 0xff. Because the maximum expected length is 8, a buffer overflow of 247 bytes occurs!
Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU. By fixing the root cause, this prevents the buffer overflow.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Missing ndo_change_mtu() in Linux hi311x CAN driver allows attackers to set an invalid MTU and send oversized CAN XL frames, causing a buffer overflow in hi3110_hw_tx().
Root
Cause
The Linux kernel's hi311x CAN driver fails to populate the net_device_ops->ndo_change_mtu() callback. This omission allows an attacker to configure an arbitrarily large MTU on the CAN interface (e.g., ip link set can0 mtu 9999). When combined with a PF_PACKET socket using the ETH_P_CANXL protocol, the attacker can bypass the CAN framework's validation and directly inject a crafted CAN XL frame into the driver's xmit() function [1][2][3].
Exploitation
To exploit the vulnerability, an attacker must have the capability to open a raw PF_PACKET socket and modify the interface MTU (typically requiring CAP_NET_ADMIN or root privileges). After setting an oversized MTU, the attacker sends a CAN XL frame with a malicious flags field (e.g., 0xff) and a len field of 2048. The driver's can_dev_dropped_skb() check only verifies that the skb protocol is ETH_P_CANXL and that the length is valid for CAN XL, but it does not verify the actual device capabilities. Consequently, the frame reaches hi3110_hard_start_xmit(), which misinterprets the CAN XL frame as a standard CAN frame and passes the frame->len (which is actually the flags field) directly to hi3110_hw_tx() [1][2][3].
Impact
In hi3110_hw_tx(), the driver performs a memcpy with frame->len as the copy size: memcpy(buf + HI3110_FIFO_EXT_DATA_OFF, frame->data, frame->len). Since frame->len is controlled by the attacker (e.g., 0xff = 255 bytes), but the expected maximum is 8 bytes, this results in a buffer overflow of 247 bytes beyond the intended buffer. This overflow can corrupt adjacent kernel memory, potentially leading to a denial of service (system crash) or, under specific conditions, arbitrary code execution [1][2][3].
Mitigation
The vulnerability is fixed by populating ndo_change_mtu() to restrict the MTU to CAN_MTU (the maximum size for a standard CAN frame). This prevents the attacker from setting an invalid MTU and thus blocks the attack vector. The fix has been applied to the Linux kernel stable branches; users should update to the latest patched kernels [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
8f2c247e958108f351db6b2367ab85762274c57d332ce8c92be1b25005fd0def814b4ba31e77fdf9e33a8ac1c7656fa71Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
8- git.kernel.org/stable/c/57d332ce8c921d0e340650470bb0c1d707f216eenvd
- git.kernel.org/stable/c/7ab85762274c0fa997f0ef9a2307b2001aae43c4nvd
- git.kernel.org/stable/c/8f351db6b2367991f0736b2cff082f5de4872113nvd
- git.kernel.org/stable/c/ac1c7656fa717f29fac3ea073af63f0b9919ec9anvd
- git.kernel.org/stable/c/be1b25005fd0f9d4e78bec6695711ef87ee33398nvd
- git.kernel.org/stable/c/def814b4ba31b563584061d6895d5ff447d5bc14nvd
- git.kernel.org/stable/c/e77fdf9e33a83a08f04ab0cb68c19ddb365a622fnvd
- git.kernel.org/stable/c/f2c247e9581024d8b3dd44cbe086bf2bebbef42cnvd
News mentions
0No linked articles in our index yet.