SECUFOCUSNOW
Home›CVE index›CVE-2025-39987
Review reviewHigh

CVE-2025-39987

Linux

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,...

CVSS
7.8
EPSS
0.16%
6.07% percentile
CISA KEV
Not listed
Published
2025.10.15
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.16%
Technical severityCVSS 7.8

Vulnerability overview

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,...

Affected product and versions

Product
Linux
Affected versions
>= 57e83fb9b7468c75cb65cde1d23043553c346c6d < f2c247e9581024d8b3dd44cbe086bf2bebbef42c, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < 8f351db6b2367991f0736b2cff082f5de4872113, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < 7ab85762274c0fa997f0ef9a2307b2001aae43c4, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < 57d332ce8c921d0e340650470bb0c1d707f216ee, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < be1b25005fd0f9d4e78bec6695711ef87ee33398, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < def814b4ba31b563584061d6895d5ff447d5bc14, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < e77fdf9e33a83a08f04ab0cb68c19ddb365a622f, >= 57e83fb9b7468c75cb65cde1d23043553c346c6d < ac1c7656fa717f29fac3ea073af63f0b9919ec9a, >= 4.12
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available