CVE-2025-39873 Details
Description
In the Linux kernel, the following vulnerability has been resolved: can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB can_put_echo_skb() takes ownership of the SKB and it may be freed during or after the call. However, xilinx_can xcan_write_frame() keeps using SKB after the call. Fix that by only calling can_put_echo_skb() after the code is done touching the SKB. The tx_lock is held for the entire xcan_write_frame() execution and also on the can_get_echo_skb() side so the order of operations does not matter. An earlier fix commit 3d3c817c3a40 ("can: xilinx_can: Fix usage of skb memory") did not move the can_put_echo_skb() call far enough. [mkl: add "commit" in front of sha1 in patch description] [mkl: fix indention]
A use-after-free vulnerability has been identified in the Xilinx CAN driver of the Linux kernel. The issue arises in the 'xcan_write_frame()' function, where the 'can_put_echo_skb()' call, which takes ownership of the socket buffer (SKB) and may free it, is made before the function has finished using the SKB. This flaw can lead to the driver accessing freed memory, potentially causing instability or exploitation. The vulnerability affects the Linux kernel stable tree.
Users can upgrade to the latest version of the Linux kernel where this vulnerability has been fixed. The specific commit addressing this issue is 'ef79f00be72bd81d2e1e6f060d83cf7e425deee4', which is included in the official Linux kernel repositories.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/1139321161a3ba5e45e61e0738b37f42f20bc57a | kernel.org | Patch |
| https://git.kernel.org/stable/c/668cc1e3bb21101d074e430de1b7ba8fd10189e7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/725b33deebd6e4c96fe7893f384510a54258f28f | kernel.org | Patch |
| https://git.kernel.org/stable/c/94b050726288a56a6b8ff55aa641f2fedbd3b44c | kernel.org | Patch |
| https://git.kernel.org/stable/c/e202ffd9e54538ef67ec301ebd6d9da4823466c9 | kernel.org | Patch |
| https://git.kernel.org/stable/c/ef79f00be72bd81d2e1e6f060d83cf7e425deee4 | kernel.org | Patch |
| https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html | CVE | Mailing ListThird Party Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-416 | Use After Free | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.19, < 5.15.194 >= 5.16, < 6.1.153 >= 6.2, < 6.6.107 >= 6.7, < 6.12.48 >= 6.13, < 6.16.8 6.17 rc1 6.17 rc2 6.17 rc3 6.17 rc4 6.17 rc5 |
CPE
Remediation
| |
| debian debian linux | 11.0 |
CPE
Remediation
| |
Change History
7 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 19, 2026 | CVE Translated | [email protected] |
| Jul 30, 2026 | CVE Modified | kernel.org |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 20, 2026 | Initial Analysis | [email protected] |
| Nov 3, 2025 | CVE Modified | CVE |
| Oct 2, 2025 | CVE Modified | kernel.org |
| Sep 23, 2025 | New CVE Received | kernel.org |