Linux kernel use-after-free in xen-netback statistics
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < 37d5a73170579b30e67cc8b19ec69715eea3a6b6| No fix yet |
| Linux Linux | — |
|
In the Linux kernel, the following vulnerability has been resolved:
xen-netback: Fix UAF when reading statistics data
The network statistic data in the driver is protected by RCU. Unfortunately when tearing down the queues after an error during connecting to the frontend (e.g. due to illegal Xenstore data filled in by the guest), the statistic data is being freed without synchronizing the RCU state. In case the data is being read via sysfs in this phase, access to already freed memory or memory being in new use is possible.
Fix that by calling synchronize_net() before freeing the queue data.
This is XSA-526 / CVE-2026-100080
From the CVE record · Linux
The Linux kernel’s xen-netback driver can free network statistics data without waiting for ongoing readers when queue teardown follows an error connecting to a Xen frontend. If a guest supplies illegal Xenstore data and the statistics are read through sysfs during teardown, the read may access freed or repurposed memory.
Engineers running the Linux kernel with xen-netback should check whether their installation is affected; affected versions were not specified.