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

> A missing unregister call in the vmxnet3 driver reset path causes a kernel warning and potential crash, requiring a patch to fix.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Apr 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-62583, BELL-CVE-2025-22106, DEBIAN-CVE-2025-22106, GHSA-646x-rjhr-jf76, ROOT-OS-DEBIAN-13-CVE-2025-22106, ROOT-OS-UBUNTU-2404-CVE-2025-22106, UBUNTU-CVE-2025-22106

## What is CVE-2025-22106?

CVE-2025-22106 is a medium-severity vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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().

## Which versions are affected by CVE-2025-22106?

It affects 1 product.


Products: Linux kernel.

## How do I fix CVE-2025-22106?

Apply the vendor's patch.

## Is CVE-2025-22106 being exploited?

There is no known exploitation of CVE-2025-22106 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22106 and fix it if it is affected.

What it is: CVE-2025-22106 is a medium-severity vulnerability in Linux kernel, published on 16 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-22106 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-22106/ (Markdown: https://insights.sbomify.com/CVE-2025-22106/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-22106
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-22106
- OSV: https://osv.dev/vulnerability/CVE-2025-22106

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-22106/
Summaries are generated and may contain mistakes; the official description above is the record.