# CVE-2022-49687: virtio_net: fix xdp_rxq_info bug after suspend/resume

Status: published. Published: 2025-02-26. Updated: 2026-11-05.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- 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). Source: 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). Source: CNA: Linux

## Severity and prioritization

- CISA KEV: No listing in collected sources

- EPSS: 0.29% as of 2026-11-05; percentile 21.58%

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/9222672fa6370f0ec3d899662cb8680e9282fc4c (CNA: Linux)

- https://git.kernel.org/stable/c/8c7a32b7c15555beddc5810c3334d9cefff061bf (CNA: Linux)

- https://git.kernel.org/stable/c/340fbdc8011f2dc678f622c5ce1cbb5ab8305de7 (CNA: Linux)

- https://git.kernel.org/stable/c/8d7fe9ad6fddc2af8bde4b921b4f8fab231ed38c (CNA: Linux)

- https://git.kernel.org/stable/c/57ee40f1b198b59d43c216fbc4672f9300d3c8b0 (CNA: Linux)

- https://git.kernel.org/stable/c/8af52fe9fd3bf5e7478da99193c0632276e1dfce (CNA: Linux)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2022-49687; retrieved 2026-11-05; source updated 2026-11-05

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2022-49687; retrieved 2026-11-05; source updated Not reported

Revision: 761981f4457fa759e4b359af676a9b96ec712592a0fe4ce2b3e22ca30a202d57

Canonical: https://y2.dev/cve/CVE-2022-49687

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.