CVE-2025-39873

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-09-23. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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]

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

September 23, 2025

Last Modified

July 30, 2026

Advisory Details (7)

Auto-updated Jul 30, 2026
Patch available.
generic Patch Available

[SECURITY] [DLA 4328-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ef79f00be72bd81d2e1e6f060d83cf7e425deee4
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e202ffd9e54538ef67ec301ebd6d9da4823466c9
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/94b050726288a56a6b8ff55aa641f2fedbd3b44c
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/725b33deebd6e4c96fe7893f384510a54258f28f
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/668cc1e3bb21101d074e430de1b7ba8fd10189e7
generic

can: xilinx_can: xcan_write_frame(): fix use-after-free of transmitted SKB - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1139321161a3ba5e45e61e0738b37f42f20bc57a

Vendor Advisories for CVE-2025-39873(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(25)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.170.159) @ jammy2026-05-29ubuntu
ubuntulinux-tools-realtime-5.15 (5.15.0.1099.103) @ jammy2026-05-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1095.95) @ jammy2026-05-29ubuntu
ubuntulinux-tools-oracle-lts-22.04 (5.15.0.1097.93) @ jammy2026-05-29ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1100.90) @ jammy2026-05-29ubuntu
ubuntulinux-tools-intel-iotg-5.15 (5.15.0.1095.95) @ jammy2026-05-29ubuntu
ubuntulinux-tools-aws-edge (5.15.0.1100.107~20.04.1) @ focal2026-05-29ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1052.52) @ jammy2026-05-29ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1064 (5.15.0-1064.68) @ jammy2026-05-29ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1041.43) @ jammy2026-05-29ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1049.52.1) @ noble2026-05-29ubuntu
ubuntulinux-virtual-6.8 (6.8.0-106.106) @ noble2026-05-29ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1052.55+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1045.46) @ noble2026-05-29ubuntu
ubuntulinux-tools-aws-edge (6.8.0-1050.53~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1051.57) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-fips-5.15 (5.15.0.1109.94) @ jammy2026-05-29ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1097.95) @ jammy2026-05-29ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1051.57~22.04.1) @ jammy2026-05-29ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2040.41) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1052.58+fips1) @ noble2026-05-29ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1109.107) @ jammy2026-05-29ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1110.119~20.04.1) @ focal2026-05-29ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1029.30) @ noble2026-05-29ubuntu
linuxKernel @ 5.15.194—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-01 04:15 UTCEPSS rescore
  2. 2026-07-30 16:27 UTCEPSS rescore
  3. 2026-07-30 06:51 UTCEG score recompute
  4. 2026-07-30 06:51 UTCVendor advisory
  5. 2026-07-30 06:51 UTCGHSA enrichment
  6. 2026-07-30 01:29 UTCEPSS rescore
  7. 2026-07-28 15:35 UTCEPSS rescore
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-24 14:17 UTCEPSS rescore
  11. 2026-07-23 19:41 UTCOSV refresh
  12. 2026-07-23 02:55 UTCEG score recompute
  13. 2026-07-22 14:07 UTCEPSS rescore
  14. 2026-07-22 14:07 UTCEPSS rescore
  15. 2026-07-21 15:24 UTCEPSS rescore
  16. 2026-07-20 17:07 UTCEPSS rescore
  17. 2026-07-19 14:30 UTCEPSS rescore
  18. 2026-07-19 14:30 UTCEPSS rescore
  19. 2026-07-19 02:28 UTCEPSS rescore
  20. 2026-07-19 02:28 UTCEPSS rescore
  21. 2026-07-16 17:02 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 01:59 UTCEPSS rescore
  25. 2026-07-15 01:59 UTCEPSS rescore
Show 72 more
  1. 2026-07-13 22:29 UTCEPSS rescore
  2. 2026-07-13 22:29 UTCEPSS rescore
  3. 2026-07-13 06:12 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-09 19:09 UTCEPSS rescore
  8. 2026-07-09 19:09 UTCEPSS rescore
  9. 2026-07-07 13:45 UTCEPSS rescore
  10. 2026-07-06 16:27 UTCEPSS rescore
  11. 2026-07-06 16:27 UTCEPSS rescore
  12. 2026-07-06 13:41 UTCOSV refresh
  13. 2026-07-06 02:23 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 06:30 UTCEPSS rescore
  16. 2026-07-01 15:06 UTCEPSS rescore
  17. 2026-07-01 15:06 UTCEPSS rescore
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 23:22 UTCEPSS rescore
  20. 2026-06-29 14:06 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 14:07 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-28 04:55 UTCEPSS rescore
  26. 2026-06-27 03:08 UTCEPSS rescore
  27. 2026-06-27 03:08 UTCEPSS rescore
  28. 2026-06-25 13:49 UTCEPSS rescore
  29. 2026-06-25 13:49 UTCEPSS rescore
  30. 2026-06-24 14:04 UTCEPSS rescore
  31. 2026-06-24 14:04 UTCEPSS rescore
  32. 2026-06-23 21:32 UTCEPSS rescore
  33. 2026-06-23 21:32 UTCEPSS rescore
  34. 2026-06-22 14:25 UTCEPSS rescore
  35. 2026-06-22 14:25 UTCEPSS rescore
  36. 2026-06-21 14:56 UTCEPSS rescore
  37. 2026-06-21 14:56 UTCEPSS rescore
  38. 2026-06-21 01:59 UTCEPSS rescore
  39. 2026-06-21 01:59 UTCEPSS rescore
  40. 2026-06-19 19:25 UTCEPSS rescore
  41. 2026-06-19 19:25 UTCEPSS rescore
  42. 2026-06-18 17:52 UTCEPSS rescore
  43. 2026-06-18 17:52 UTCEPSS rescore
  44. 2026-06-18 02:05 UTCOSV refresh
  45. 2026-06-17 17:52 UTCEPSS rescore
  46. 2026-06-16 17:52 UTCEPSS rescore
  47. 2026-06-16 17:52 UTCEPSS rescore
  48. 2026-06-14 23:17 UTCEPSS rescore
  49. 2026-06-13 23:00 UTCEPSS rescore
  50. 2026-06-12 23:11 UTCEPSS rescore
  51. 2026-06-11 14:00 UTCEPSS rescore
  52. 2026-06-10 22:18 UTCEPSS rescore
  53. 2026-06-10 13:22 UTCEPSS rescore
  54. 2026-06-08 14:16 UTCEPSS rescore
  55. 2026-06-08 14:16 UTCEPSS rescore
  56. 2026-06-07 15:24 UTCEPSS rescore
  57. 2026-06-06 13:47 UTCEPSS rescore
  58. 2026-06-06 13:47 UTCEPSS rescore
  59. 2026-06-05 22:46 UTCEPSS rescore
  60. 2026-06-05 22:46 UTCEPSS rescore
  61. 2026-06-04 13:12 UTCEPSS rescore
  62. 2026-06-04 13:12 UTCEPSS rescore
  63. 2026-06-02 20:12 UTCEPSS rescore
  64. 2026-06-01 13:51 UTCEPSS rescore
  65. 2026-06-01 13:51 UTCEPSS rescore
  66. 2026-05-31 22:30 UTCEPSS rescore
  67. 2026-05-31 22:30 UTCEPSS rescore
  68. 2026-05-31 00:16 UTCEPSS rescore
  69. 2026-05-29 22:10 UTCEG score recompute
  70. 2026-05-29 22:10 UTCVendor advisory
  71. 2026-05-29 22:10 UTCGHSA enrichment
  72. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-39873?
CVE-2025-39873 is a high vulnerability published on September 23, 2025. In the Linux kernel, the following vulnerability has been resolved: can: xilinxcan: xcanwrite_frame(): fix use-after-free of transmitted SKB canputecho_skb() takes ownership of the SKB and it may be freed during or after the call. However, xilinxcan xcanwrite_frame() keeps using SKB after the call.…
When was CVE-2025-39873 disclosed?
CVE-2025-39873 was first published in the National Vulnerability Database on September 23, 2025, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-39873 actively exploited?
CVE-2025-39873 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 95.5% of all scored CVEs.
What is the CVSS score of CVE-2025-39873?
CVE-2025-39873 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-39873?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-39873, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-39873

Explore →

Is Your Infrastructure Affected by CVE-2025-39873?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs