Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-39986can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow

Description

In the Linux kernel, the following vulnerability has been resolved: can: sun4i_can: 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, sun4ican_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN frame. This can result in a buffer overflow. The driver will consume cf->len as-is with no further checks on this line: dlc = cf->len; Here, cf->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 a couple line below when doing: for (i = 0; i < dlc; i++) writel(cf->data[i], priv->base + (dreg + i * 4)); 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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39986, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.18% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 063539db42203b29d5aa2adf0cae3d68c646a6b6
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 4f382cc887adca8478b9d3e6b81aa6698a95fff4
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 60463a1c138900494cb3adae41142a11cd8feb3c
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < a61ff7ac93270d20ca426c027d6d01c8ac8e904c
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 2e423e1990f3972cbea779883fef52c2f2acb858
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < de77841652e57afbc46e9e1dbf51ee364fc008e1
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 7f7b21026a6febdb749f6f6f950427245aa86cce
    • affected 0738eff14d817a02ab082c392c96a1613006f158 – < 61da0bd4102c459823fbe6b8b43b01fb6ace4a22
  • Linux · Linux

    • affected 4.4
    • unaffected < 4.4
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.155 – ≤ 6.1.*
    • unaffected 6.6.109 – ≤ 6.6.*
    • unaffected 6.12.50 – ≤ 6.12.*
    • unaffected 6.16.10 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39986 badge
[![CVE-2025-39986](https://cveledger.app/badge/CVE-2025-39986.svg)](https://cveledger.app/cve/CVE-2025-39986)

Record last updated .