CVE-2025-38464

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2025-22677 (ENISA EUVD) · GHSA-vwv2-838r-2q6p (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

tipc: Fix use-after-free in tipc_conn_close().

syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0]

tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each tipc_conn.

The problem is that tipc_conn_close() is called after releasing the IDR lock.

At the same time, there might be tipc_conn_recv_work() running and it could call tipc_conn_close() for the same tipc_conn and release its last ->kref.

Once we release the IDR lock in tipc_topsrv_stop(), there is no guarantee that the tipc_conn is alive.

Let's hold the ref before releasing the lock and put the ref after tipc_conn_close() in tipc_topsrv_stop().

[0]: BUG: KASAN: use-after-free in tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 Read of size 8 at addr ffff888099305a08 by task kworker/u4:3/435

CPU: 0 PID: 435 Comm: kworker/u4:3 Not tainted 4.19.204-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: netns cleanup_net Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1fc/0x2ef lib/dump_stack.c:118 print_address_description.cold+0x54/0x219 mm/kasan/report.c:256 kasan_report_error.cold+0x8a/0x1b9 mm/kasan/report.c:354 kasan_report mm/kasan/report.c:412 [inline] __asan_report_load8_noabort+0x88/0x90 mm/kasan/report.c:433 tipc_conn_close+0x122/0x140 net/tipc/topsrv.c:165 tipc_topsrv_stop net/tipc/topsrv.c:701 [inline] tipc_topsrv_exit_net+0x27b/0x5c0 net/tipc/topsrv.c:722 ops_exit_list+0xa5/0x150 net/core/net_namespace.c:153 cleanup_net+0x3b4/0x8b0 net/core/net_namespace.c:553 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Allocated by task 23: kmem_cache_alloc_trace+0x12f/0x380 mm/slab.c:3625 kmalloc include/linux/slab.h:515 [inline] kzalloc include/linux/slab.h:709 [inline] tipc_conn_alloc+0x43/0x4f0 net/tipc/topsrv.c:192 tipc_topsrv_accept+0x1b5/0x280 net/tipc/topsrv.c:470 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

Freed by task 23: __cache_free mm/slab.c:3503 [inline] kfree+0xcc/0x210 mm/slab.c:3822 tipc_conn_kref_release net/tipc/topsrv.c:150 [inline] kref_put include/linux/kref.h:70 [inline] conn_put+0x2cd/0x3a0 net/tipc/topsrv.c:155 process_one_work+0x864/0x1570 kernel/workqueue.c:2153 worker_thread+0x64c/0x1130 kernel/workqueue.c:2296 kthread+0x33f/0x460 kernel/kthread.c:259 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415

The buggy address belongs to the object at ffff888099305a00 which belongs to the cache kmalloc-512 of size 512 The buggy address is located 8 bytes inside of 512-byte region [ffff888099305a00, ffff888099305c00) The buggy address belongs to the page: page:ffffea000264c140 count:1 mapcount:0 mapping:ffff88813bff0940 index:0x0 flags: 0xfff00000000100(slab) raw: 00fff00000000100 ffffea00028b6b88 ffffea0002cd2b08 ffff88813bff0940 raw: 0000000000000000 ffff888099305000 0000000100000006 0000000000000000 page dumped because: kasan: bad access detected

Memory state around the buggy address: ffff888099305900: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888099305980: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc >ffff888099305a00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ^ ffff888099305a80: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb ffff888099305b00: fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb fb

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
12th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 25, 2025

Last Modified

August 5, 2026

Advisory Details (10)

Auto-updated Jul 30, 2026
Patch available.
Web pageMentions a patch (unverified)

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

https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4327-1] linux security update

https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dab8ded2e5ff41012a6ff400b44dbe76ccf3592a
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/be4b8392da7978294f2f368799d29dd509fb6c4d
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/667eeab4999e981c96b447a4df5f20bdf5c26f13
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/50aa2d121bc2cfe2d825f8a331ea75dfaaab6a50
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b89e17b2fd64012682bed158d9eb3d2e96dec42
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1dbf7cd2454a28b1da700085b99346b5445aeabb
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15a6f4971e2f157d57e09ea748d1fbc714277aa4
Web page

tipc: Fix use-after-free in tipc_conn_close(). - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/03dcdd2558e1e55bf843822fe4363dcb48743f2b

Vendor Advisories for CVE-2025-38464(12)

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

Patch Availability(31)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-kvm-5.15 (5.15.0.1088.84) @ jammy2026-10-25ubuntu
ubuntulinux-tools-nvidia-tegra-igx-rt-5.15 (5.15.0.1034.36) @ jammy2026-10-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1046.52+fips1) @ noble2026-10-25ubuntu
ubuntuoracle (6.8.0-1005) @ noble2026-10-25ubuntu
ubuntulinux-tools-gcp-edge (6.8.0-1047.50~22.04.2) @ jammy2026-10-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.14.0-36.36) @ plucky2026-10-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-100.100~22.04.1) @ jammy2026-10-25ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1056 (5.15.0-1056.60) @ jammy2026-10-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1043.44) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1096.94) @ jammy2026-10-25ubuntu
ubuntulinux-tools-raspi-6.14 (6.14.0-1018.18) @ plucky2026-10-25ubuntu
ubuntulinux-tools-gcp-fips-5.15 (5.15.0.1092.82) @ jammy2026-10-25ubuntu
ubuntulinux-tools-realtime-hwe-24.04-edge (6.14.0-1016.16~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-tools-oem-6.14 (6.14.0-1016.16) @ noble2026-10-25ubuntu
ubuntulinux-tools-oracle-edge (6.14.0-1017.17~24.04.1) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-6.14 (6.14.0-1017.17) @ plucky2026-10-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-100.100) @ noble2026-10-25ubuntu
redhatkernel-0:5.14.0-70.146.1.el9_02025-09-11redhat
redhatkernel-0:4.18.0-305.172.1.el8_42025-09-11redhat
redhatkernel-0:5.14.0-427.88.1.el9_42025-09-11redhat
redhatkernel-0:4.18.0-193.168.1.el8_22025-09-10redhat
redhatkernel-rt-0:5.14.0-70.146.1.rt21.218.el9_02025-09-10redhat
redhatkernel-0:4.18.0-372.160.1.el8_62025-09-10redhat
redhatkernel-rt-0:5.14.0-284.136.1.rt14.421.el9_22025-09-04redhat
redhatkernel-0:5.14.0-284.136.1.el9_22025-09-04redhat
redhatkernel-0:4.18.0-477.108.1.el8_82025-09-02redhat
redhatkernel-0:5.14.0-570.39.1.el9_62025-09-02redhat
redhatkernel-0:6.12.0-55.30.1.el10_02025-09-02redhat
redhatkernel-0:4.18.0-553.72.1.el8_102025-09-02redhat
redhatkernel-rt-0:4.18.0-553.72.1.rt7.413.el8_102025-09-02redhat
linuxKernel @ 5.4.296 (fixes >=3.11.0)—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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (46 versions)
  • every version up to 5.10.244-1: fixed in 5.10.244-1
—
linux-6.16.1.106-3~deb11u1 ... 6.1.148-1~deb11u1 (11 versions)
  • every version up to 6.1.153-1~deb11u1: fixed in 6.1.153-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (41 versions)
  • every version up to 6.1.147-1: fixed in 6.1.147-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1
  • every version up to 6.12.41-1: fixed in 6.12.41-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.16~rc7-1~exp1 (62 versions)
  • every version up to 6.16.3-1: fixed in 6.16.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

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 10× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 200 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 102 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2025-38464?
CVE-2025-38464 is a high-severity vulnerability; its CVE record was published on July 25, 2025. In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free in tipc_conn_close(). syzbot reported a null-ptr-deref in tipc_conn_close() during netns dismantle. [0] tipc_topsrv_stop() iterates tipc_net(net)->topsrv->conn_idr and calls tipc_conn_close() for each…
When was the CVE record for CVE-2025-38464 published?
The CVE record for CVE-2025-38464 was published on July 25, 2025. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2025-38464 actively exploited?
CVE-2025-38464 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (12th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-38464?
CVE-2025-38464 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-38464?
A fix for CVE-2025-38464 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-38464 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-38464

Explore →

Is Your Infrastructure Affected by CVE-2025-38464?

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

Book a Demo →Browse All CVEs