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…

PriorityP431high7.1CVSS 3.1

AVLACLPRLUINSUCHINAH

EPSS

0.29%

21.2th percentile

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)

# 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.

Affected

18 ranges

Vendor	Product	Version range	Fixed in
debian	linux	< linux 5.18.14-1 (bookworm)	linux 5.18.14-1 (bookworm)
linux	linux	—	—
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 9222672fa6370f0ec3d899662cb8680e9282fc4c	9222672fa6370f0ec3d899662cb8680e9282fc4c
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 8c7a32b7c15555beddc5810c3334d9cefff061bf	8c7a32b7c15555beddc5810c3334d9cefff061bf
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 340fbdc8011f2dc678f622c5ce1cbb5ab8305de7	340fbdc8011f2dc678f622c5ce1cbb5ab8305de7
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c	8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 57ee40f1b198b59d43c216fbc4672f9300d3c8b0	57ee40f1b198b59d43c216fbc4672f9300d3c8b0
linux	linux	>= 754b8a21a96d5f11712245aef907149606b323ae < 8af52fe9fd3bf5e7478da99193c0632276e1dfce	8af52fe9fd3bf5e7478da99193c0632276e1dfce
linux	linux_kernel	—	—
linux	linux_kernel	>= 0 < 5.10.127-1	5.10.127-1
linux	linux_kernel	>= 0 < 5.18.14-1	5.18.14-1
linux	linux_kernel	>= 0 < 5.18.14-1	5.18.14-1
linux	linux_kernel	>= 0 < 5.18.14-1	5.18.14-1
linux	linux_kernel	>= 4.16 < 4.19.250	4.19.250
linux	linux_kernel	>= 4.20 < 5.4.202	5.4.202
linux	linux_kernel	>= 5.11 < 5.15.51	5.15.51
linux	linux_kernel	>= 5.16 < 5.18.8	5.18.8
linux	linux_kernel	>= 5.5 < 5.10.127	5.10.127

CVSS provenance

nvdv3.17.1HIGHCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H

osv7.1HIGH

vendor_debian7.1HIGH

vendor_redhat7.1HIGH

Stop checking back — get the weekly exploitation signal.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.