CVE-2025-39988: can: etas_es58x: 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 38c0abad45b190a30d8284a37264d2127a6ec303, 72de0facc50afdb101fb7197d880407f1abfc77f, b26cccd87dcddc47b450a40f3b1ac3fe346efcff.
Low priority for now. Upgrade to Linux Linux 38c0abad45b190a30d8284a37264d2127a6ec303, 72de0facc50afdb101fb7197d880407f1abfc77f, b26cccd87dcddc47b450a40f3b1ac3fe346efcff 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: etas_es58x: 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 etas_es58x 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, es58x_start_xmit() receives a CAN XL frame which it is not able to correctly handle and will thus misinterpret it as a CAN(FD) frame. This can result in a buffer overflow. For example, using the es581.4 variant, the frame will be dispatched to es581_4_tx_can_msg(), go through the last check at the beginning of this function: if (can_is_canfd_skb(skb)) return -EMSGSIZE; and reach this line: memcpy(tx_can_msg->data, cf->data, 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! Populate net_device_ops->ndo_change_mtu() to ensure that the interface's MTU can not be set to anything bigger than CAN_MTU or CANFD_MTU (depending on the device capabilities). 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
- 5.13affected
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before 72de0facc50afdb101fb7197d880407f1abfc77faffected · git
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before c4e582e686c4d683c87f2b4a316385b3d81d370faffected · git
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before cbc1de71766f326a44bb798aeae4a7ef4a081cc9affected · git
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before b26cccd87dcddc47b450a40f3b1ac3fe346efcffaffected · git
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before e587af2c89ecc6382c518febea52fa9ba81e47c0affected · git
- 8537257874e949a59c834cecfd5a063e11b64b0b and later · before 38c0abad45b190a30d8284a37264d2127a6ec303affected · git
- before 5.13not affected · semver
- 5.15.194 and later · up to and including 5.15.*not affected · semver
- 6.1.155 and later · up to and including 6.1.*not 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-39986Oct 15, 2025 · can: sun4i_can: populate ndo_change_mtu() to prevent buffer overflow31Monitor
- ← EarlierCVE-2025-39987Oct 15, 2025 · can: hi311x: populate ndo_change_mtu() to prevent buffer overflow31Monitor
- Later →CVE-2025-39990Oct 15, 2025 · bpf: Check the helper function is valid in get_helper_proto31Monitor
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 | 38c0abad45b190a30d8284a37264d2127a6ec303 | Vendor (CNA) |
| Linux Linux | 72de0facc50afdb101fb7197d880407f1abfc77f | Vendor (CNA) |
| Linux Linux | b26cccd87dcddc47b450a40f3b1ac3fe346efcff | Vendor (CNA) |
| Linux Linux | c4e582e686c4d683c87f2b4a316385b3d81d370f | Vendor (CNA) |
| Linux Linux | cbc1de71766f326a44bb798aeae4a7ef4a081cc9 | Vendor (CNA) |
| Linux Linux | e587af2c89ecc6382c518febea52fa9ba81e47c0 | Vendor (CNA) |
| 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 (5 more)Show less
- git.kernel.org/stable/c/72de0facc50afdb101fb7197d880407f1abfc77f
- git.kernel.org/stable/c/b26cccd87dcddc47b450a40f3b1ac3fe346efcff
- git.kernel.org/stable/c/c4e582e686c4d683c87f2b4a316385b3d81d370f
- git.kernel.org/stable/c/cbc1de71766f326a44bb798aeae4a7ef4a081cc9
- git.kernel.org/stable/c/e587af2c89ecc6382c518febea52fa9ba81e47c0
Vendor advisories and official records. Exploit/PoC links are deliberately left out.