Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2025-39985— can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow

EPSS 0.07% · P22
Get alerts for future matching vulnerabilitiesLog in to subscribe

I. Basic Information for CVE-2025-39985

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
can: mcba_usb: populate ndo_change_mtu() to prevent buffer overflow
Source: NVD (National Vulnerability Database)
Vulnerability Description
In the Linux kernel, the following vulnerability has been resolved: can: mcba_usb: 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 mcba_usb 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, mcba_usb_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 these lines: usb_msg.dlc = cf->len; memcpy(usb_msg.data, cf->data, usb_msg.dlc); 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. By fixing the root cause, this prevents the buffer overflow.
Source: NVD (National Vulnerability Database)
CVSS Information
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Type
N/A
Source: NVD (National Vulnerability Database)
Vulnerability Title
Linux kernel 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Linux kernel是美国Linux基金会的开源操作系统Linux所使用的内核。 Linux kernel存在安全漏洞,该漏洞源于mcba_usb驱动未实现ndo_change_mtu函数,可能导致缓冲区溢出攻击。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

VendorProductAffected VersionsCPESubscribe
LinuxLinux 51f3baad7de943780ce0c17bd7975df567dd6e14 ~ 0fa9303c4b9493727e0d3a6ac3729300e3013930 -
LinuxLinux 4.12 -

II. Public POCs for CVE-2025-39985

#POC DescriptionSource LinkShenlong Link
AI-Generated POCPremium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2025-39985

登录查看更多情报信息。

Same Patch Batch · Linux · 2025-10-15 · 34 CVEs total

CVE-2025-39973i40e: add validation for ring_len param
CVE-2025-39981Bluetooth: MGMT: Fix possible UAFs
CVE-2025-39979net/mlx5: fs, fix UAF in flow counter release
CVE-2025-39980nexthop: Forbid FDB status change while nexthop is in a group
CVE-2025-39978octeontx2-pf: Fix potential use after free in otx2_tc_add_flow()
CVE-2025-39977futex: Prevent use-after-free during requeue-PI
CVE-2025-39976futex: Use correct exit on failure from futex_hash_allocate_default()
CVE-2025-39975smb: client: fix wrong index reference in smb2_compound_op()
CVE-2025-39974tracing/osnoise: Fix slab-out-of-bounds in _parse_integer_limit()
CVE-2025-39982Bluetooth: hci_event: Fix UAF in hci_acl_create_conn_sync
CVE-2025-39972i40e: fix idx validation in i40e_validate_queue_map
CVE-2025-39970i40e: fix input validation logic for action_meta
CVE-2025-39971i40e: fix idx validation in config queues msg
CVE-2025-39969i40e: fix validation of VF state in get resources
CVE-2025-39968i40e: add max boundary check for VF filters
CVE-2025-39967fbcon: fix integer overflow in fbcon_do_set_font
CVE-2025-39966iommufd: Fix race during abort for file descriptors
CVE-2025-40000wifi: rtw89: fix use-after-free in rtw89_core_tx_kick_off_and_wait()
CVE-2025-39984net: tun: Update napi->skb after XDP process
CVE-2025-39983Bluetooth: hci_event: Fix UAF in hci_conn_tx_dequeue

Showing top 20 of 34 CVEs. View all on vendor page → →

IV. Related Vulnerabilities

V. Comments for CVE-2025-39985

No comments yet


Leave a comment