CVE-2022-49687

HIGH EPSS 19.1%
Published Feb 26, 20251y ago · Modified Jun 17, 20262w ago
7.1 CVSS 3.1
High
Find Similar
Published Feb 26, 2025 1y ago
Last Modified Jun 17, 2026 2w ago

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.

CVSS Details

Base Score
7.1
Exploitability
1.8
Impact
5.2
Vector string
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
Attack Vector Local
Attack Complexity Low
Privileges Required Low
User Interaction None
Scope Unchanged
Confidentiality High
Integrity None
Availability High

Threat Intelligence

EPSS Exploit Probability
19.1% percentile
Exploit & Patch Status
No Known Exploit
Patch Available

Affected Products 8

VendorProductVersionRange
linuxlinux_kernel*≥4.16  –  <4.19.250
linuxlinux_kernel*≥4.20  –  <5.4.202
linuxlinux_kernel*≥5.5  –  <5.10.127
linuxlinux_kernel*≥5.11  –  <5.15.51
linuxlinux_kernel*≥5.16  –  <5.18.8
linuxlinux_kernel5.19any
linuxlinux_kernel5.19any
linuxlinux_kernel5.19any

References 6

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

Remediation

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