CVE-2022-49687

  1. OpenCVE
  2. Vulnerabilities (CVE)
  3. CVE-2022-49687
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.

7.1 /10

CVSS v3 : HIGH

V3 Legend

Vector :

Exploitability : 1.8 / Impact : 5.2

Attack Vector LOCAL

Attack Complexity LOW

Privileges Required LOW

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact HIGH

Scope UNCHANGED

References
Link Resource
https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 Patch
https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 Patch
https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce Patch
https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf Patch
https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c Patch
https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c Patch
Configurations

Configuration 1 (hide)

OR cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
History

22 Jan 2026, 20:55

Type Values Removed Values Added
Summary
  • (es) En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: virtio_net: corrección del error xdp_rxq_info después de suspender/reanudar La siguiente secuencia actualmente provoca una advertencia de error del controlador al usar virtio_net: # ip link set eth0 up # echo mem &gt; /sys/power/state (or e.g. # rtcwake -s 10 -m mem) # 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. Esto significa que podemos solucionar esto fácilmente y evitar este tipo de problemas en el futuro simplemente llamando a virtnet_close()/open() desde los controladores de congelación/restauración. Aparte de agregar las llamadas xdp_rxq_info faltantes, la única diferencia es que el trabajo de recarga solo se cancela si se ejecuta netif_running(). Sin embargo, esto no debería generar ninguna diferencia funcional, ya que el trabajo de recarga solo debería estar activo si la interfaz de red está realmente activa.
References () https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 - () https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 - Patch
References () https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 - () https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 - Patch
References () https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce - () https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce - Patch
References () https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf - () https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf - Patch
References () https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c - () https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c - Patch
References () https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c - () https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c - Patch
CVSS v2 : unknown
v3 : unknown 		v2 : unknown
v3 : 7.1
CWE NVD-CWE-noinfo
CPE cpe:2.3:o:linux:linux_kernel:5.19:rc2:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.19:rc3:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:5.19:rc1:*:*:*:*:*:*
cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*
First Time Linux
Linux linux Kernel

26 Feb 2025, 07:01

Type Values Removed Values Added
New CVE
Information

Published : 2025-02-26 07:01

Updated : 2026-01-22 20:55

NVD link : CVE-2022-49687

Mitre link : CVE-2022-49687

CVE.ORG link : CVE-2022-49687

JSON object : View

Products Affected

linux

  • linux_kernel
CWE
NVD-CWE-noinfo