CVE-2022-49687 Details
Description
In the Linux kernel, the following vulnerability has been resolved: virtio_net: fix xdp_rxq_info bug after suspend/resume The following sequence currently causes a driver bug warning when using virtio_net: # ip link set eth0 up # echo mem > /sys/power/state (or e.g. # rtcwake -s 10 -m mem) <resume> # ip link set eth0 down Missing register, driver bug WARNING: CPU: 0 PID: 375 at net/core/xdp.c:138 xdp_rxq_info_unreg+0x58/0x60 Call trace: xdp_rxq_info_unreg+0x58/0x60 virtnet_close+0x58/0xac __dev_close_many+0xac/0x140 __dev_change_flags+0xd8/0x210 dev_change_flags+0x24/0x64 do_setlink+0x230/0xdd0 ... This happens because virtnet_freeze() frees the receive_queue completely (including struct xdp_rxq_info) but does not call xdp_rxq_info_unreg(). Similarly, virtnet_restore() sets up the receive_queue again but does not call xdp_rxq_info_reg(). Actually, parts of virtnet_freeze_down() and virtnet_restore_up() are almost identical to virtnet_close() and virtnet_open(): only the calls to xdp_rxq_info_(un)reg() are missing. This means that we can fix this easily and avoid such problems in the future by just calling virtnet_close()/open() from the freeze/restore handlers. Aside from adding the missing xdp_rxq_info calls the only difference is that the refill work is only cancelled if netif_running(). However, this should not make any functional difference since the refill work should only be active if the network interface is actually up.
A vulnerability has been identified in the Linux kernel's virtio_net component, related to the handling of the XDP (eXpress Data Path) receive queue information after a suspend and resume cycle. The issue arises because the virtnet_freeze function frees the receive queue, including the XDP receive queue information, without properly unregistering it. When the network interface is brought down, a driver bug warning is generated, indicating that the XDP receive queue information was not correctly managed. This vulnerability can lead to driver bugs and warnings, disrupting normal network operations.
The vulnerability can be addressed by modifying the virtio_net driver's suspend and resume handlers to include the missing XDP receive queue registration and unregistration calls. This adjustment will ensure that the receive queue information is properly managed during suspend and resume cycles, preventing the driver bug warnings and associated network issues.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 | kernel.org | Patch |
| https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 | kernel.org | Patch |
| https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce | kernel.org | Patch |
| https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf | kernel.org | Patch |
| https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c | kernel.org | Patch |
| https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.16, < 4.19.250 >= 4.20, < 5.4.202 >= 5.5, < 5.10.127 >= 5.11, < 5.15.51 >= 5.16, < 5.18.8 5.19 rc1 5.19 rc2 5.19 rc3 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 22, 2026 | Initial Analysis | [email protected] |
| Feb 26, 2025 | New CVE Received | kernel.org |