Linux Kernel up to 6.16.9 hi311x ndo_change_mtu buffer overflow

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability has been found in Linux Kernel up to 6.16.9 and classified as critical. Affected by this vulnerability is the function ndo_change_mtu of the component hi311x. The manipulation leads to buffer overflow. This vulnerability is referenced as CVE-2025-39987. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in Linux Kernel up to 6.16.9. It has been rated as critical. This issue affects the function ndo_change_mtu of the component hi311x. The manipulation with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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). 2. 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.

The advisory is shared at git.kernel.org. The identification of this vulnerability is CVE-2025-39987 since 04/16/2025. The exploitation is known to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/08/2026).

The vulnerability scanner Nessus provides a plugin with the ID 271542 (Linux Distros Unpatched Vulnerability : CVE-2025-39987), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 5.4.300, 5.10.245, 5.15.194, 6.1.155, 6.6.109, 6.12.50 or 6.16.10 eliminates this vulnerability. Applying the patch f2c247e9581024d8b3dd44cbe086bf2bebbef42c/8f351db6b2367991f0736b2cff082f5de4872113/7ab85762274c0fa997f0ef9a2307b2001aae43c4/57d332ce8c921d0e340650470bb0c1d707f216ee/be1b25005fd0f9d4e78bec6695711ef87ee33398/def814b4ba31b563584061d6895d5ff447d5bc14/e77fdf9e33a83a08f04ab0cb68c19ddb365a622f/ac1c7656fa717f29fac3ea073af63f0b9919ec9a is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (271542) and CERT Bund (WID-SEC-2025-2298). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Affected

  • Google Container-Optimized OS
  • Debian Linux
  • Amazon Linux 2
  • Red Hat Enterprise Linux
  • Ubuntu Linux
  • SUSE Linux
  • Oracle Linux
  • SUSE openSUSE
  • RESF Rocky Linux
  • Open Source Linux Kernel
  • IBM QRadar SIEM
  • Dell NetWorker

Productinfo

Type

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.0
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.0
VulDB Temp Score: 7.6
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Buffer overflow
CWE: CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒

Physical: No
Local: No
Remote: Partially

Availability: 🔒
Status: Not defined

EPSS Score: 🔒
EPSS Percentile: 🔒

Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 271542
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2025-39987

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔒

Upgrade: Kernel 5.4.300/5.10.245/5.15.194/6.1.155/6.6.109/6.12.50/6.16.10
Patch: f2c247e9581024d8b3dd44cbe086bf2bebbef42c/8f351db6b2367991f0736b2cff082f5de4872113/7ab85762274c0fa997f0ef9a2307b2001aae43c4/57d332ce8c921d0e340650470bb0c1d707f216ee/be1b25005fd0f9d4e78bec6695711ef87ee33398/def814b4ba31b563584061d6895d5ff447d5bc14/e77fdf9e33a83a08f04ab0cb68c19ddb365a622f/ac1c7656fa717f29fac3ea073af63f0b9919ec9a

Timelineinfo

04/16/2025 CVE reserved
10/15/2025 +182 days Advisory disclosed
10/15/2025 +0 days VulDB entry created
02/08/2026 +116 days VulDB entry last update

Sourcesinfo

Vendor: kernel.org

Advisory: git.kernel.org
Status: Confirmed

CVE: CVE-2025-39987 (🔒)
GCVE (CVE): GCVE-0-2025-39987
GCVE (VulDB): GCVE-100-328625
CERT Bund: WID-SEC-2025-2298 - Linux Kernel: Mehrere Schwachstellen

Entryinfo

Created: 10/15/2025 12:05
Updated: 02/08/2026 20:15
Changes: 10/15/2025 12:05 (59), 10/27/2025 15:49 (2), 11/03/2025 18:47 (7), 11/22/2025 16:50 (1), 12/21/2025 07:39 (1), 02/08/2026 20:15 (1)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you know our Splunk app?

Download it now for free!