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]

Metrics

No CVSS v4.0

Attack Vector Local

Attack Complexity Low

Privileges Required Low

Scope Unchanged

Confidentiality Impact None

Integrity Impact None

Availability Impact High

User Interaction None

No CVSS v3.0

No CVSS v2

This CVE is not in the KEV list.

Key SSVC decision points have not yet been added.

Affected Vendors & Products

Vendors Products
Linux
  • Linux Kernel

No data.

No data.

References
Link Providers
https://git.kernel.org/stable/c/1139321161a3ba5e45e61e0738b37f42f20bc57a cve-icon cve-icon
https://git.kernel.org/stable/c/668cc1e3bb21101d074e430de1b7ba8fd10189e7 cve-icon cve-icon
https://git.kernel.org/stable/c/725b33deebd6e4c96fe7893f384510a54258f28f cve-icon cve-icon
https://git.kernel.org/stable/c/94b050726288a56a6b8ff55aa641f2fedbd3b44c cve-icon cve-icon
https://git.kernel.org/stable/c/e202ffd9e54538ef67ec301ebd6d9da4823466c9 cve-icon cve-icon
https://git.kernel.org/stable/c/ef79f00be72bd81d2e1e6f060d83cf7e425deee4 cve-icon cve-icon
https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html cve-icon
https://lore.kernel.org/linux-cve-announce/2025092300-CVE-2025-39873-94d3@gregkh/T cve-icon
https://nvd.nist.gov/vuln/detail/CVE-2025-39873 cve-icon
https://www.cve.org/CVERecord?id=CVE-2025-39873 cve-icon
History

Mon, 03 Nov 2025 18:30:00 +0000

Type Values Removed Values Added
References

Thu, 02 Oct 2025 13:45:00 +0000

Type Values Removed Values Added
References

Wed, 24 Sep 2025 00:15:00 +0000

Type Values Removed Values Added
References
Metrics threat_severity

None

 cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}

threat_severity

Moderate

Tue, 23 Sep 2025 16:15:00 +0000

Type Values Removed Values Added
First Time appeared Linux
Linux linux Kernel
Vendors & Products Linux
Linux linux Kernel

Tue, 23 Sep 2025 06:15:00 +0000

Type Values Removed Values Added
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]
Title can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB
References
cve-icon MITRE

Status: PUBLISHED

Assigner: Linux

Published: 2025-09-23T06:00:46.157Z

Updated: 2025-11-03T17:44:20.103Z

Reserved: 2025-04-16T07:20:57.144Z

Link: CVE-2025-39873

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2025-09-23T06:15:46.670

Modified: 2025-11-03T18:16:51.370

Link: CVE-2025-39873

cve-icon Redhat

Severity : Moderate

Publid Date: 2025-09-23T00:00:00Z

Links: CVE-2025-39873 - Bugzilla