CVE-2022-49687
virtio_net: fix xdp_rxq_info bug after suspend/resume
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.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| Linux Linux |
≥ 754b8a21a96d5f11712245aef907149606b323ae; < 9222672fa6370f0ec3d899662cb8680e9282fc4c (affected, git) ≥ 754b8a21a96d5f11712245aef907149606b323ae; < 8c7a32b7c15555beddc5810c3334d9cefff061bf (affected, git) ≥ 754b8a21a96d5f11712245aef907149606b323ae; < 340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 (affected, git) ≥ 754b8a21a96d5f11712245aef907149606b323ae; < 8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c (affected, git) ≥ 754b8a21a96d5f11712245aef907149606b323ae; < 57ee40f1b198b59d43c216fbc4672f9300d3c8b0 (affected, git) ≥ 754b8a21a96d5f11712245aef907149606b323ae; < 8af52fe9fd3bf5e7478da99193c0632276e1dfce (affected, git) Other versions: unaffected |
CNA: Linux |
| Linux Linux |
4.16 (affected) ≥ 0; < 4.16 (unaffected, semver) ≥ 4.19.250; ≤ 4.19.* (unaffected, semver) ≥ 5.4.202; ≤ 5.4.* (unaffected, semver) ≥ 5.10.127; ≤ 5.10.* (unaffected, semver) ≥ 5.15.51; ≤ 5.15.* (unaffected, semver) ≥ 5.18.8; ≤ 5.18.* (unaffected, semver) ≥ 5.19; ≤ * (unaffected, original_commit_for_fix) Other versions: affected |
CNA: Linux |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
No CVSS assessment reported. An unscored record is not a low-severity determination.
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4cCNA: Linux
- https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bfCNA: Linux
- https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7CNA: Linux
- https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38cCNA: Linux
- https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0CNA: Linux
- https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfceCNA: Linux
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.