Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2025-38109: net/mlx5: Fix ECVF vports unload on shutdown flow

HighCVSS 7.8 · v3.1—No exploit Fix available

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.19% (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 24db585d369f949f698e03d7d8017e5ae19d0497, 5953ae44dfe5dbad374318875be834c3b7b71ee6, 687560d8a9a2d654829ad0da1ec24242f1de711d; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.1-1.

Low priority for now. Upgrade to Linux Linux 24db585d369f949f698e03d7d8017e5ae19d0497, 5953ae44dfe5dbad374318875be834c3b7b71ee6, 687560d8a9a2d654829ad0da1ec24242f1de711d; azl3 kernel 6.6.92.2-2 on Azure Linux 3.0 6.6.96.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: net/mlx5: Fix ECVF vports unload on shutdown flow Fix shutdown flow UAF when a virtual function is created on the embedded chip (ECVF) of a BlueField device. In such case the vport acl ingress table is not properly destroyed. ECVF functionality is independent of ecpf_vport_exists capability and thus functions mlx5_eswitch_(enable|disable)_pf_vf_vports() should not test it when enabling/disabling ECVF vports. kernel log: [] refcount_t: underflow; use-after-free. [] WARNING: CPU: 3 PID: 1 at lib/refcount.c:28 refcount_warn_saturate+0x124/0x220 ---------------- [] Call trace: [] refcount_warn_saturate+0x124/0x220 [] tree_put_node+0x164/0x1e0 [mlx5_core] [] mlx5_destroy_flow_table+0x98/0x2c0 [mlx5_core] [] esw_acl_ingress_table_destroy+0x28/0x40 [mlx5_core] [] esw_acl_ingress_lgcy_cleanup+0x80/0xf4 [mlx5_core] [] esw_legacy_vport_acl_cleanup+0x44/0x60 [mlx5_core] [] esw_vport_cleanup+0x64/0x90 [mlx5_core] [] mlx5_esw_vport_disable+0xc0/0x1d0 [mlx5_core] [] mlx5_eswitch_unload_ec_vf_vports+0xcc/0x150 [mlx5_core] [] mlx5_eswitch_disable_sriov+0x198/0x2a0 [mlx5_core] [] mlx5_device_disable_sriov+0xb8/0x1e0 [mlx5_core] [] mlx5_sriov_detach+0x40/0x50 [mlx5_core] [] mlx5_unload+0x40/0xc4 [mlx5_core] [] mlx5_unload_one_devl_locked+0x6c/0xe4 [mlx5_core] [] mlx5_unload_one+0x3c/0x60 [mlx5_core] [] shutdown+0x7c/0xa4 [mlx5_core] [] pci_device_shutdown+0x3c/0xa0 [] device_shutdown+0x170/0x340 [] __do_sys_reboot+0x1f4/0x2a0 [] __arm64_sys_reboot+0x2c/0x40 [] invoke_syscall+0x78/0x100 [] el0_svc_common.constprop.0+0x54/0x184 [] do_el0_svc+0x30/0xac [] el0_svc+0x48/0x160 [] el0t_64_sync_handler+0xa4/0x12c [] el0t_64_sync+0x1a4/0x1a8 [] --[ end trace 9c4601d68c70030e ]---

Published
Jul 3, 2025
Updated
Jun 17, 2026
EPSS
0.1% · 9th percentile

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
total

Vulnrichment: CISA's decision-tree inputs.

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-38109

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 every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • 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, at most 30 a day (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.

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.

VendorProduct
linuxlinux kernel

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

    • 6.5affected
    • a7719b29a82199b90ebbf355d3332e0fbfbf6045 and later · before 5953ae44dfe5dbad374318875be834c3b7b71ee6affected · git
    • a7719b29a82199b90ebbf355d3332e0fbfbf6045 and later · before da15ca0553325acf68039015f2f4db750c8e2b96affected · git
    • a7719b29a82199b90ebbf355d3332e0fbfbf6045 and later · before 24db585d369f949f698e03d7d8017e5ae19d0497affected · git
    • a7719b29a82199b90ebbf355d3332e0fbfbf6045 and later · before 687560d8a9a2d654829ad0da1ec24242f1de711daffected · git
    • before 6.5not affected · semver
    • 6.6.94 and later · up to and including 6.6.*not affected · semver
    • 6.12.34 and later · up to and including 6.12.*not affected · semver
    • 6.15.3 and later · up to and including 6.15.*not affected · semver
    • 6.16 and laternot affected · original_commit_for_fix

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.49.1.el10_16.12.0-124.49.1.el10_1
AlmaLinux:10kernel-docbefore 6.12.0-124.49.1.el10_16.12.0-124.49.1.el10_1
AlmaLinux:9kernelbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64kbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-debug-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modulesbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-64k-modules-extrabefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-abi-stablelistsbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-cross-headersbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debugbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-corebefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-develbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7
AlmaLinux:9kernel-debug-devel-matchedbefore 5.14.0-611.47.1.el9_75.14.0-611.47.1.el9_7

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2025-38101Jul 3, 2025 · ring-buffer: Fix buffer locking in ring_buffer_subbuf_order_set()
    31Monitor
  • ← EarlierCVE-2025-38106Jul 3, 2025 · io_uring: fix use-after-free of sq->thread in __io_uring_show_fdinfo()
    31Monitor
  • Later →CVE-2025-38114Jul 3, 2025 · e1000: Move cancel_work_sync to avoid deadlock
    22Monitor

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 Linux24db585d369f949f698e03d7d8017e5ae19d0497Vendor (CNA)
Linux Linux5953ae44dfe5dbad374318875be834c3b7b71ee6Vendor (CNA)
Linux Linux687560d8a9a2d654829ad0da1ec24242f1de711dVendor (CNA)
Linux Linuxda15ca0553325acf68039015f2f4db750c8e2b96Vendor (CNA)
azl3 kernel 6.6.92.2-2 on Azure Linux 3.06.6.96.1-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel-matched5.14.0-611.47.1.el9_7 · AlmaLinux:9Package registry (OSV)
debian:linux6.12.35-1 · Debian:13Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-611.47.1.el9_7 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)

+13

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.

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

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)

CWE-416 · Use After Free

CVSS vector

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

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

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.

References

All records