Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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]

Timeline

  1. ID reserved

    By Linux

  2. · 5 months later

    Published

  3. · 11 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-39873, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Modified3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < e202ffd9e54538ef67ec301ebd6d9da4823466c9
    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < 1139321161a3ba5e45e61e0738b37f42f20bc57a
    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < 94b050726288a56a6b8ff55aa641f2fedbd3b44c
    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < 725b33deebd6e4c96fe7893f384510a54258f28f
    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < 668cc1e3bb21101d074e430de1b7ba8fd10189e7
    • affected 1598efe57b3e768056e4ca56cb9cf33111e68d1c – < ef79f00be72bd81d2e1e6f060d83cf7e425deee4
  • Linux · Linux

    • affected 4.19
    • unaffected < 4.19
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.153 – ≤ 6.1.*
    • unaffected 6.6.107 – ≤ 6.6.*
    • unaffected 6.12.48 – ≤ 6.12.*
    • unaffected 6.16.8 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References7

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-39873 badge
[![CVE-2025-39873](https://cveledger.app/badge/CVE-2025-39873.svg)](https://cveledger.app/cve/CVE-2025-39873)

Record last updated .