Linux kernel double unmap in xen-netback ring cleanup
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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
From the CVE record · Linux
The Linux kernel’s xen-netback component can attempt to unmap frontend data rings twice if mapping fails while a ring is already mapped. The input does not specify the resulting impact or whether exploitation requires network access, authentication, or user interaction.
Engineers running Linux kernels with xen-netback should check whether their kernel is affected; no affected versions are specified.