CVE-2025-40064

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2025-10-28. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2025-36464 (ENISA EUVD) · GHSA-c442-5cxr-p4xq (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.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

smc: Fix use-after-free in __pnet_find_base_ndev().

syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0]

smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes down to pnet_find_base_ndev(), where RTNL is held. Then, UAF happened at __pnet_find_base_ndev() when the dev is first used.

This means dev had already been freed before acquiring RTNL in pnet_find_base_ndev().

While dev is going away, dst->dev could be swapped with blackhole_netdev, and the dev's refcnt by dst will be released.

We must hold dev's refcnt before calling smc_pnet_find_ism_resource().

Also, smc_pnet_find_roce_resource() has the same problem.

Let's use __sk_dst_get() and dst_dev_rcu() in the two functions.

[0]: BUG: KASAN: use-after-free in __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 Read of size 1 at addr ffff888036bac33a by task syz.0.3632/18609

CPU: 1 UID: 0 PID: 18609 Comm: syz.0.3632 Not tainted syzkaller #0 PREEMPT(full) Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/18/2025 Call Trace: dump_stack_lvl+0x189/0x250 lib/dump_stack.c:120 print_address_description mm/kasan/report.c:378 [inline] print_report+0xca/0x240 mm/kasan/report.c:482 kasan_report+0x118/0x150 mm/kasan/report.c:595 __pnet_find_base_ndev+0x1b1/0x1c0 net/smc/smc_pnet.c:926 pnet_find_base_ndev net/smc/smc_pnet.c:946 [inline] smc_pnet_find_ism_by_pnetid net/smc/smc_pnet.c:1103 [inline] smc_pnet_find_ism_resource+0xef/0x390 net/smc/smc_pnet.c:1154 smc_find_ism_device net/smc/af_smc.c:1030 [inline] smc_find_proposal_devices net/smc/af_smc.c:1115 [inline] __smc_connect+0x372/0x1890 net/smc/af_smc.c:1545 smc_connect+0x877/0xd90 net/smc/af_smc.c:1715 __sys_connect_file net/socket.c:2086 [inline] __sys_connect+0x313/0x440 net/socket.c:2105 __do_sys_connect net/socket.c:2111 [inline] __se_sys_connect net/socket.c:2108 [inline] __x64_sys_connect+0x7a/0x90 net/socket.c:2108 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7f47cbf8eba9 Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f47ccdb1038 EFLAGS: 00000246 ORIG_RAX: 000000000000002a RAX: ffffffffffffffda RBX: 00007f47cc1d5fa0 RCX: 00007f47cbf8eba9 RDX: 0000000000000010 RSI: 0000200000000280 RDI: 000000000000000b RBP: 00007f47cc011e19 R08: 0000000000000000 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 R13: 00007f47cc1d6038 R14: 00007f47cc1d5fa0 R15: 00007ffc512f8aa8

The buggy address belongs to the physical page: page: refcount:0 mapcount:0 mapping:0000000000000000 index:0xffff888036bacd00 pfn:0x36bac flags: 0xfff00000000000(node=0|zone=1|lastcpupid=0x7ff) raw: 00fff00000000000 ffffea0001243d08 ffff8880b863fdc0 0000000000000000 raw: ffff888036bacd00 0000000000000000 00000000ffffffff 0000000000000000 page dumped because: kasan: bad access detected page_owner tracks the page as freed page last allocated via order 2, migratetype Unmovable, gfp_mask 0x446dc0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOWARN|__GFP_RETRY_MAYFAIL|__GFP_COMP), pid 16741, tgid 16741 (syz-executor), ts 343313197788, free_ts 380670750466 set_page_owner include/linux/page_owner.h:32 [inline] post_alloc_hook+0x240/0x2a0 mm/page_alloc.c:1851 prep_new_page mm/page_alloc.c:1859 [inline] get_page_from_freelist+0x21e4/0x22c0 mm/page_alloc.c:3858 __alloc_frozen_pages_noprof+0x181/0x370 mm/page_alloc.c:5148 alloc_pages_mpol+0x232/0x4a0 mm/mempolicy.c:2416 ___kmalloc_large_node+0x5f/0x1b0 mm/slub.c:4317 __kmalloc_large_node_noprof+0x18/0x90 mm/slub.c:4348 __do_kmalloc_node mm/slub.c:4364 [inline] __kvmalloc_node ---truncated---

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.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.1%
EPSS %ILE
4th
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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

October 28, 2025

Last Modified

October 19, 2026

Advisory Details (2)

Auto-updated Jul 31, 2026
Patch available.
Web page

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

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

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

https://git.kernel.org/stable/c/233927b645cb7a14bb98d23ac72e4c7243a9f0d9

Vendor Advisories for CVE-2025-40064(13)

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

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-azure-6.17 (6.17.0-1008.8) @ questing2026-10-27ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.17.0-14.14) @ questing2026-10-27ubuntu
ubuntulinux-tools-gcp-64k-6.17 (6.17.0-1007.7) @ questing2026-10-27ubuntu
ubuntulinux-tools-oracle-64k-6.17 (6.17.0-1007.7) @ questing2026-10-27ubuntu
ubuntulinux-tools-oem-6.17 (6.17.0-1011.11) @ noble2026-10-27ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-10-27ubuntu
redhatkernel-0:5.14.0-687.44.1.el9_82026-09-04redhat
redhatkernel-0:5.14.0-570.123.1.el9_62026-06-22redhat
redhatkernel-0:4.18.0-193.195.1.el8_22026-04-22redhat
redhatkernel-0:4.18.0-305.189.1.el8_42026-04-22redhat
redhatkernel-0:4.18.0-372.188.1.el8_62026-04-22redhat
redhatkernel-0:4.18.0-477.135.1.el8_82026-04-08redhat
redhatkernel-0:6.12.0-55.63.1.el10_02026-03-09redhat
redhatkernel-rt-0:4.18.0-553.107.1.rt7.448.el8_102026-02-23redhat
redhatkernel-0:4.18.0-553.107.1.el8_102026-02-23redhat
redhatkernel-0:6.12.0-124.38.1.el10_12026-02-16redhat
redhatkernel-0:5.14.0-611.34.1.el9_72026-02-16redhat
linuxKernel @ 6.1.187 (fixes >=4.19.0)—osv
linuxKernel @ 6.17.3 (fixes >=4.19.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:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (56 versions)
  • every version up to 6.1.187-1: fixed in 6.1.187-1
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.17.5-1~exp1 (76 versions)
  • every version up to 6.17.6-1: fixed in 6.17.6-1
—

Additional Vendor Advisories

(6)

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2025-40064?
CVE-2025-40064 is a high-severity vulnerability; its CVE record was published on October 28, 2025. In the Linux kernel, the following vulnerability has been resolved: smc: Fix use-after-free in __pnet_find_base_ndev(). syzbot reported use-after-free of net_device in __pnet_find_base_ndev(), which was called during connect(). [0] smc_pnet_find_ism_resource() fetches sk_dst_get(sk)->dev and passes…
When was the CVE record for CVE-2025-40064 published?
The CVE record for CVE-2025-40064 was published on October 28, 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 October 19, 2026; the record at its source may have been updated since.
Is CVE-2025-40064 actively exploited?
CVE-2025-40064 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-40064?
CVE-2025-40064 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-40064?
A fix for CVE-2025-40064 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-40064 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-40064

Explore →

Is Your Infrastructure Affected by CVE-2025-40064?

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

Book a Demo →Browse All CVEs