Riskcovery

CVE-2025-39873

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB

State
Published
Severity
7.8 High
Published
Sep 23, 2025
Updated
Aug 5, 2026
Reserved
Apr 16, 2025

Read the record on cve.org

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]

Scores

CVSSScoreVectorSource
3.17.8 HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HLinux

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before e202ffd9e54538ef67ec301ebd6d9da4823466c9Affected
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before 1139321161a3ba5e45e61e0738b37f42f20bc57aAffected
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before 94b050726288a56a6b8ff55aa641f2fedbd3b44cAffected
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before 725b33deebd6e4c96fe7893f384510a54258f28fAffected
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before 668cc1e3bb21101d074e430de1b7ba8fd10189e7Affected
  • 1598efe57b3e768056e4ca56cb9cf33111e68d1c to before ef79f00be72bd81d2e1e6f060d83cf7e425deee4Affected
LinuxLinux
  • 4.19Affected
  • before 4.19Not affected
  • 5.15.194 through 5.15.*Not affected
  • 6.1.153 through 6.1.*Not affected
  • 6.6.107 through 6.6.*Not affected
  • 6.12.48 through 6.12.*Not affected
  • 6.16.8 through 6.16.*Not affected
  • 6.17 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.