{"id":"CVE-2022-49687","summary":"virtio_net: fix xdp_rxq_info bug after suspend/resume","details":"In the Linux kernel, the following vulnerability has been resolved:\n\nvirtio_net: fix xdp_rxq_info bug after suspend/resume\n\nThe following sequence currently causes a driver bug warning\nwhen using virtio_net:\n\n  # ip link set eth0 up\n  # echo mem \u003e /sys/power/state (or e.g. # rtcwake -s 10 -m mem)\n  \u003cresume\u003e\n  # ip link set eth0 down\n\n  Missing register, driver bug\n  WARNING: CPU: 0 PID: 375 at net/core/xdp.c:138 xdp_rxq_info_unreg+0x58/0x60\n  Call trace:\n   xdp_rxq_info_unreg+0x58/0x60\n   virtnet_close+0x58/0xac\n   __dev_close_many+0xac/0x140\n   __dev_change_flags+0xd8/0x210\n   dev_change_flags+0x24/0x64\n   do_setlink+0x230/0xdd0\n   ...\n\nThis happens because virtnet_freeze() frees the receive_queue\ncompletely (including struct xdp_rxq_info) but does not call\nxdp_rxq_info_unreg(). Similarly, virtnet_restore() sets up the\nreceive_queue again but does not call xdp_rxq_info_reg().\n\nActually, parts of virtnet_freeze_down() and virtnet_restore_up()\nare almost identical to virtnet_close() and virtnet_open(): only\nthe calls to xdp_rxq_info_(un)reg() are missing. This means that\nwe can fix this easily and avoid such problems in the future by\njust calling virtnet_close()/open() from the freeze/restore handlers.\n\nAside from adding the missing xdp_rxq_info calls the only difference\nis that the refill work is only cancelled if netif_running(). However,\nthis should not make any functional difference since the refill work\nshould only be active if the network interface is actually up.","modified":"2026-04-02T08:27:50.438440Z","published":"2025-02-26T02:24:13.187Z","related":["SUSE-SU-2025:1027-1","SUSE-SU-2025:1176-1","SUSE-SU-2025:1183-1","SUSE-SU-2025:1194-1","SUSE-SU-2025:1241-1","SUSE-SU-2025:1263-1","SUSE-SU-2025:1293-1"],"database_specific":{"cna_assigner":"Linux","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49687.json"},"references":[{"type":"WEB","url":"https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7"},{"type":"WEB","url":"https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf"},{"type":"WEB","url":"https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c"},{"type":"WEB","url":"https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/49xxx/CVE-2022-49687.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-49687"},{"type":"PACKAGE","url":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","events":[{"introduced":"754b8a21a96d5f11712245aef907149606b323ae"},{"fixed":"9222672fa6370f0ec3d899662cb8680e9282fc4c"},{"fixed":"8c7a32b7c15555beddc5810c3334d9cefff061bf"},{"fixed":"340fbdc8011f2dc678f622c5ce1cbb5ab8305de7"},{"fixed":"8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c"},{"fixed":"57ee40f1b198b59d43c216fbc4672f9300d3c8b0"},{"fixed":"8af52fe9fd3bf5e7478da99193c0632276e1dfce"}]}],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-49687.json"}}],"schema_version":"1.7.5"}