Skip to content
statance
MenuClose
unknown

CVE-2026-99287

xen-netback: Zero out sring pointers on unmap

Published 10 Nov 2026 · Source updated 16 Nov 2026 · Retrieved 2026-11-19 05:48 UTC

Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

In the Linux kernel, the following vulnerability has been resolved:

xen-netback: Zero out sring pointers on unmap

If xenvif_map_frontend_data_rings() fails when a ring is already mapped, it unmaps them via xenvif_unmap_frontend_data_rings() which keeps the ring pointers unchanged. xenvif_connect_data()'s cleanup path calls xenvif_disconnect_queue() which in turn calls xenvif_unmap_frontend_data_rings() again, which will attempt to unmap the pointers a second time.

Zero out the ring pointers after they are unmapped to avoid this issue.

This is XSA-532

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
LinuxLinuxaffected: 2ac061ce97f413bfbbdd768f7d2e0fda2e8170df to < 87fd475dc4e354088f6534285388e7b061f54b35; affected: 2ac061ce97f413bfbbdd768f7d2e0fda2e8170df to < c5f54af611ff6fe1d53fa05d8e87b469dc56122b; affected: 2ac061ce97f413bfbbdd768f7d2e0fda2e8170df to < e7ba61734d6ad6adfd5bf617052e590743211669; affected: 2ac061ce97f413bfbbdd768f7d2e0fda2e8170df to < f96f16592a32430a0582309d73a873b6d3ee2bdbSee vendor advisory
LinuxLinuxaffected: 5.5; unaffected: 0 to < 5.5; unaffected: 6.12.117 to ≤ 6.12.*; unaffected: 6.18.63 to ≤ 6.18.*; unaffected: 7.3.4 to ≤ 7.3.*; unaffected: 7.4-rc3 to ≤ *See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-19 21:16 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed