LiveActive security incident?Get immediate response
CVE Record

CVE-2025-22106: vmxnet3: unregister xdp rxq info in the reset path

In the Linux kernel, the following vulnerability has been resolved: vmxnet3: unregister xdp rxq info in the reset path vmxnet3 does not unregister xdp rxq info in the vmxnet3_reset_work() code path as vmxnet3_rq_destroy() is not invoked in this code path. So, we get below message with a backtrace. Missing unregister, handled but fix driver WARNING: CPU:48 PID: 500 at net/core/xdp.c:182 __xdp_rxq_info_reg+0x93/0xf0 This patch fixes the problem by moving the unregister code of XDP from vmxnet3_rq_destroy() to vmxnet3_rq_cleanup().

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

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel vmxnet3 network driver cleanup bug. During a reset path, XDP receive-queue information was not unregistered correctly, causing a kernel warning and backtrace. The sources do not show remote code execution, privilege escalation, CVSS scoring, or active exploitation.

Executive priority

Treat as routine patch management unless affected VMware Linux guests show kernel warnings or network-driver instability. There is no source-backed evidence of active exploitation or severe security impact, but kernel fixes should still enter normal maintenance cycles.

Technical view

vmxnet3_reset_work() did not call vmxnet3_rq_destroy(), leaving XDP rxq unregister handling skipped. The kernel fix moves XDP unregister logic from vmxnet3_rq_destroy() to vmxnet3_rq_cleanup(), covering the reset path. Impact evidence is limited to kernel WARN/backtrace behavior.

Likely exposure

Exposure appears limited to Linux systems using the vmxnet3 virtual NIC driver, commonly VMware guest environments, on affected kernel versions before the stable fixes. Systems not using vmxnet3 or XDP-related paths are less likely exposed based on the supplied evidence.

Exploitation context

No supplied source reports exploitation in the wild, and the CVE is not marked KEV. The available description indicates a reliability or correctness flaw in driver reset cleanup, not a documented attacker-driven exploit path.

Researcher notes

The core issue is lifecycle cleanup coverage: reset cleanup skipped the XDP rxq unregister path. The public record lacks CVSS, CWE, exploitability detail, and distribution-specific affected package ranges, so exposure decisions should be tied to kernel commit inclusion and vendor advisories.

Mitigation direction

  • Apply vendor-supported Linux kernel updates containing the listed stable fixes.
  • Prioritize VMware guests using the vmxnet3 network driver.
  • Track distribution advisories for packaged kernel availability.
  • Avoid unsupported manual driver changes unless directed by the vendor.

Validation and detection

  • Inventory Linux hosts using the vmxnet3 network driver.
  • Compare running kernel packages against vendor advisories and listed fixes.
  • Review kernel logs for the XDP unregister warning and backtrace.
  • Confirm patched systems no longer report the vmxnet3 XDP cleanup warning.
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-22106 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
LinuxLinux54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9, 54f00cce11786742bd11e5e68c3bf85e6dc048c9unaffected
LinuxLinux6.6, 0, 6.6.108, 6.12.49, 6.14.2, 6.15affected
Weakness

CWE details

No CWE listed

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