The fix for XSA-365 includes initialization of pointers such that subsequent cleanup code wouldn't use uninitialized…
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
|
| Linux Linux |
| No fix yet |
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
|
| Linux Linux |
| No fix yet |
| Linux Linux |
| No fix yet |
| Linux Linux |
|
| No fix yet |
| Linux Linux | — |
|
The fix for XSA-365 includes initialization of pointers such that subsequent cleanup code wouldn't use uninitialized or stale values. This initialization went too far and may under certain conditions also overwrite pointers which are in need of cleaning up. The lack of cleanup would result in leaking persistent grants. The leak in turn would prevent fully cleaning up after a respective guest has died, leaving around zombie domains. All Linux versions having the fix for XSA-365 applied are vulnerable. XSA-365 was classified to affect versions back to at least 3.11.
From the CVE record · XEN
The XSA-365 fix can overwrite pointers needed for cleanup under certain conditions, leaking persistent grants. When an affected guest dies, the leak can prevent full cleanup and leave a zombie domain. The input does not specify whether exploitation requires network access, authentication, or user interaction.
Operators running any Linux version with the XSA-365 fix applied should check their systems.