LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38628: vdpa/mlx5: Fix release of uninitialized resources on error path

In the Linux kernel, the following vulnerability has been resolved: vdpa/mlx5: Fix release of uninitialized resources on error path The commit in the fixes tag made sure that mlx5_vdpa_free() is the single entrypoint for removing the vdpa device resources added in mlx5_vdpa_dev_add(), even in the cleanup path of mlx5_vdpa_dev_add(). This means that all functions from mlx5_vdpa_free() should be able to handle uninitialized resources. This was not the case though: mlx5_vdpa_destroy_mr_resources() and mlx5_cmd_cleanup_async_ctx() were not able to do so. This caused the splat below when adding a vdpa device without a MAC address. This patch fixes these remaining issues: - Makes mlx5_vdpa_destroy_mr_resources() return early if called on uninitialized resources. - Moves mlx5_cmd_init_async_ctx() early on during device addition because it can't fail. This means that mlx5_cmd_cleanup_async_ctx() also can't fail. To mirror this, move the call site of mlx5_cmd_cleanup_async_ctx() in mlx5_vdpa_free(). An additional comment was added in mlx5_vdpa_free() to document the expectations of functions called from this context. Splat: mlx5_core 0000:b5:03.2: mlx5_vdpa_dev_add:3950:(pid 2306) warning: No mac address provisioned? ------------[ cut here ]------------ WARNING: CPU: 13 PID: 2306 at kernel/workqueue.c:4207 __flush_work+0x9a/0xb0 [...] Call Trace: <TASK> ? __try_to_del_timer_sync+0x61/0x90 ? __timer_delete_sync+0x2b/0x40 mlx5_vdpa_destroy_mr_resources+0x1c/0x40 [mlx5_vdpa] mlx5_vdpa_free+0x45/0x160 [mlx5_vdpa] vdpa_release_dev+0x1e/0x50 [vdpa] device_release+0x31/0x90 kobject_cleanup+0x37/0x130 mlx5_vdpa_dev_add+0x327/0x890 [mlx5_vdpa] vdpa_nl_cmd_dev_add_set_doit+0x2c1/0x4d0 [vdpa] genl_family_rcv_msg_doit+0xd8/0x130 genl_family_rcv_msg+0x14b/0x220 ? __pfx_vdpa_nl_cmd_dev_add_set_doit+0x10/0x10 [vdpa] genl_rcv_msg+0x47/0xa0 ? __pfx_genl_rcv_msg+0x10/0x10 netlink_rcv_skb+0x53/0x100 genl_rcv+0x24/0x40 netlink_unicast+0x27b/0x3b0 netlink_sendmsg+0x1f7/0x430 __sys_sendto+0x1fa/0x210 ? ___pte_offset_map+0x17/0x160 ? next_uptodate_folio+0x85/0x2b0 ? percpu_counter_add_batch+0x51/0x90 ? filemap_map_pages+0x515/0x660 __x64_sys_sendto+0x20/0x30 do_syscall_64+0x7b/0x2c0 ? do_read_fault+0x108/0x220 ? do_pte_missing+0x14a/0x3e0 ? __handle_mm_fault+0x321/0x730 ? count_memcg_events+0x13f/0x180 ? handle_mm_fault+0x1fb/0x2d0 ? do_user_addr_fault+0x20c/0x700 ? syscall_exit_work+0x104/0x140 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7f0c25b0feca [...] ---[ end trace 0000000000000000 ]---

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2025-38628 is a Linux kernel issue in the mlx5 vDPA driver cleanup path. When adding a vDPA device without a MAC address, the kernel could try to release resources that were never initialized, causing a warning trace. Public sources do not provide a CVSS score, impact rating, or evidence of active exploitation.

Executive priority

Treat as a targeted kernel maintenance item, not an emergency based on current evidence. Prioritize patching where mlx5 vDPA is used in virtualization or high-availability environments, because kernel warnings in device-management paths can affect operational stability.

Technical view

The flaw is in vdpa/mlx5 resource teardown after mlx5_vdpa_dev_add() fails. mlx5_vdpa_free() became the common cleanup entrypoint, but mlx5_vdpa_destroy_mr_resources() and mlx5_cmd_cleanup_async_ctx() did not safely handle uninitialized state. The fix adds early return behavior for uninitialized MR resources and adjusts async context initialization/cleanup ordering.

Likely exposure

Exposure appears limited to Linux systems using the mlx5 vDPA driver and workflows that add mlx5 vDPA devices. The cited failure condition involves adding a vDPA device without a MAC address. General Linux systems not using mlx5 vDPA are less likely to be exposed, based on the provided sources.

Exploitation context

The public record describes a kernel warning/splat on an error path, triggered during vDPA device addition without a MAC address. It does not describe privilege requirements, attacker reachability, data impact, or a weaponized exploit. CISA KEV status is false in the provided bundle.

Researcher notes

Impact evidence is incomplete. The sources show an uninitialized-resource cleanup bug and kernel warning path, but no CVSS, CWE, exploitability analysis, or confirmed security consequence beyond the splat. Analysis should focus on affected kernel branches, mlx5_vdpa deployment, and whether distro kernels backported the stable commits.

Mitigation direction

  • Apply Linux kernel updates containing the referenced stable fixes when available from your distributor.
  • Prioritize systems using mlx5 vDPA or Mellanox/NVIDIA mlx5 virtualization features.
  • If vendor packages are unavailable, monitor Linux stable and distribution advisories for backports.
  • Avoid relying on ad hoc driver changes outside supported vendor kernel maintenance.

Validation and detection

  • Inventory Linux hosts for mlx5_vdpa module or vDPA usage.
  • Check running kernel versions against distributor advisories and referenced stable commits.
  • Review kernel logs for mlx5_vdpa_dev_add warnings or related cleanup traces.
  • Confirm updated kernels include the applicable upstream stable fix.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38628 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
5Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux83e445e64f48bdae3f25013e788fcf592f142576, 83e445e64f48bdae3f25013e788fcf592f142576, 83e445e64f48bdae3f25013e788fcf592f142576, 83e445e64f48bdae3f25013e788fcf592f142576unaffected
LinuxLinux6.12, 0, 6.12.42, 6.15.10, 6.16.1, 6.17affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.