[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025041622-CVE-2025-22106-259e@gregkh>
Date: Wed, 16 Apr 2025 16:13:17 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2025-22106: vmxnet3: unregister xdp rxq info in the reset path
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().
The Linux kernel CVE team has assigned CVE-2025-22106 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.6 with commit 54f00cce11786742bd11e5e68c3bf85e6dc048c9 and fixed in 6.14.2 with commit 9908541a9e235b7c5e2fbdd59910eaf9c32c3075
Issue introduced in 6.6 with commit 54f00cce11786742bd11e5e68c3bf85e6dc048c9 and fixed in 6.15-rc1 with commit 0dd765fae295832934bf28e45dd5a355e0891ed4
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2025-22106
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/net/vmxnet3/vmxnet3_drv.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/9908541a9e235b7c5e2fbdd59910eaf9c32c3075
https://git.kernel.org/stable/c/0dd765fae295832934bf28e45dd5a355e0891ed4
Powered by blists - more mailing lists