CVE-2025-39987: can: hi311x: populate ndo_change_mtu() to prevent buffer overflow
Noroxi assessment
Priority: Monitor (action score 31/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 57d332ce8c921d0e340650470bb0c1d707f216ee, 7ab85762274c0fa997f0ef9a2307b2001aae43c4, 8f351db6b2367991f0736b2cff082f5de4872113; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1.
Low priority for now. Upgrade to Linux Linux 57d332ce8c921d0e340650470bb0c1d707f216ee, 7ab85762274c0fa997f0ef9a2307b2001aae43c4, 8f351db6b2367991f0736b2cff082f5de4872113; azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 6.6.112.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 15, 2025
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- —
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 7.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.12affected
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before f2c247e9581024d8b3dd44cbe086bf2bebbef42caffected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before 8f351db6b2367991f0736b2cff082f5de4872113affected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before 7ab85762274c0fa997f0ef9a2307b2001aae43c4affected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before 57d332ce8c921d0e340650470bb0c1d707f216eeaffected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before be1b25005fd0f9d4e78bec6695711ef87ee33398affected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before def814b4ba31b563584061d6895d5ff447d5bc14affected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before e77fdf9e33a83a08f04ab0cb68c19ddb365a622faffected · git
- 57e83fb9b7468c75cb65cde1d23043553c346c6d and later · before ac1c7656fa717f29fac3ea073af63f0b9919ec9aaffected · git
- before 4.12not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.158-1 | 6.1.158-1 |
| Debian:13 | linux | before 6.12.57-1 | 6.12.57-1 |
| Debian:14 | linux | before 6.16.10-1 | 6.16.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2025-39985Oct 15, 2025 · can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow31Monitor
- ← EarlierCVE-2025-39986Oct 15, 2025 · can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow31Monitor
- Later →CVE-2025-39988Oct 15, 2025 · can: etas_es58x: populate ndo_change_mtu() to prevent buffer overflow31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 57d332ce8c921d0e340650470bb0c1d707f216ee | Vendor (CNA) |
| Linux Linux | 7ab85762274c0fa997f0ef9a2307b2001aae43c4 | Vendor (CNA) |
| Linux Linux | 8f351db6b2367991f0736b2cff082f5de4872113 | Vendor (CNA) |
| Linux Linux | ac1c7656fa717f29fac3ea073af63f0b9919ec9a | Vendor (CNA) |
| Linux Linux | be1b25005fd0f9d4e78bec6695711ef87ee33398 | Vendor (CNA) |
| Linux Linux | def814b4ba31b563584061d6895d5ff447d5bc14 | Vendor (CNA) |
| Linux Linux | e77fdf9e33a83a08f04ab0cb68c19ddb365a622f | Vendor (CNA) |
| Linux Linux | f2c247e9581024d8b3dd44cbe086bf2bebbef42c | Vendor (CNA) |
| azl3 kernel 6.6.104.2-4 on Azure Linux 3.0 | 6.6.112.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.158-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/7ab85762274c0fa997f0ef9a2307b2001aae43c4
- git.kernel.org/stable/c/8f351db6b2367991f0736b2cff082f5de4872113
- git.kernel.org/stable/c/ac1c7656fa717f29fac3ea073af63f0b9919ec9a
- git.kernel.org/stable/c/be1b25005fd0f9d4e78bec6695711ef87ee33398
- git.kernel.org/stable/c/def814b4ba31b563584061d6895d5ff447d5bc14
- git.kernel.org/stable/c/e77fdf9e33a83a08f04ab0cb68c19ddb365a622f
- git.kernel.org/stable/c/f2c247e9581024d8b3dd44cbe086bf2bebbef42c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.