Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 31/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.15% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 005a7173d8e4710646043a681af36f79ce05a29b, 08aca586482e88aab9616a3e81bc36cad22674a5, 233927b645cb7a14bb98d23ac72e4c7243a9f0d9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.

Low priority for now. Upgrade to Linux Linux 005a7173d8e4710646043a681af36f79ce05a29b, 08aca586482e88aab9616a3e81bc36cad22674a5, 233927b645cb7a14bb98d23ac72e4c7243a9f0d9; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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: <TASK> 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 </TASK> 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---

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Oct 28, 2025
Updated
Oct 19, 2026
EPSS
0.1% · 4th percentile
CWE
—

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · Linux
7.8
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-40064

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 4.19affected
    • 0afff91c6f5ecef27715ea71e34dc2baacba1060 and later · before 005a7173d8e4710646043a681af36f79ce05a29baffected · git
    • 0afff91c6f5ecef27715ea71e34dc2baacba1060 and later · before 302dbed4760bcd19a661cc1c282d91bb7481307eaffected · git
    • 0afff91c6f5ecef27715ea71e34dc2baacba1060 and later · before 08aca586482e88aab9616a3e81bc36cad22674a5affected · git
    • 0afff91c6f5ecef27715ea71e34dc2baacba1060 and later · before 233927b645cb7a14bb98d23ac72e4c7243a9f0d9affected · git
    • 0afff91c6f5ecef27715ea71e34dc2baacba1060 and later · before 3d3466878afd8d43ec0ca2facfbc7f03e40d0f79affected · git
    • before 4.19not affected · semver
    • 6.1.187 and later · up to and including 6.1.*not affected · semver
    • 6.6.156 and later · up to and including 6.6.*not affected · semver
    • 6.12.108 and later · up to and including 6.12.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-124.38.1.el10_16.12.0-124.38.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.38.1.el10_16.12.0-124.38.1.el10_1
AlmaLinux:8bpftoolbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.107.1.el8_104.18.0-553.107.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.107.1.rt7.448.el8_104.18.0-553.107.1.rt7.448.el8_10

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-40062Oct 28, 2025 · crypto: hisilicon/qm - set NULL to qm->debug.qm_diff_regs
    0Monitor
  • ← EarlierCVE-2025-40063Oct 28, 2025 · crypto: comp - Use same definition of context alloc and free ops
    28Monitor
  • Later →CVE-2025-40065Oct 28, 2025 · RISC-V: KVM: Write hgatp register with valid mode bits
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux005a7173d8e4710646043a681af36f79ce05a29bVendor (CNA)
Linux Linux08aca586482e88aab9616a3e81bc36cad22674a5Vendor (CNA)
Linux Linux233927b645cb7a14bb98d23ac72e4c7243a9f0d9Vendor (CNA)
Linux Linux302dbed4760bcd19a661cc1c282d91bb7481307eVendor (CNA)
Linux Linux3d3466878afd8d43ec0ca2facfbc7f03e40d0f79Vendor (CNA)
azl3 kernel 6.6.152.1-1 on Azure Linux 3.06.6.157.1-1 · Release NotesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.34.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-abi-stablelists6.12.0-124.38.1.el10_1 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-doc6.12.0-124.38.1.el10_1 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.111-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)
red hat:kernel-debuginfo0:6.12.0-124.38.1.el10_1 · Red Hat:enterprise_linux:10.1Package registry (OSV)

+3

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records