Xenstore: Guests can cause Xenstore to not free temporary memory When working on a request of a guest, xenstored might need to allocate quite large amounts of memory temporarily. This memory is freed only after the request has been finished completely. A request is regarded to be finished only after the guest has read the response message of the request from the ring page. Thus a guest not reading the response can cause xenstored to not free the temporary memory. This can result in memory shortages causing Denial of Service (DoS) of xenstored.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Debian | 12 | all | xen | < 4.16.2+90-g0d39a6d1ae-1 | xen_4.16.2+90-g0d39a6d1ae-1_all.deb |
Debian | 11 | all | xen | < 4.14.5+86-g1c354767d5-1 | xen_4.14.5+86-g1c354767d5-1_all.deb |
Debian | 10 | all | xen | <= 4.11.4+107-gef32c7afa2-1 | xen_4.11.4+107-gef32c7afa2-1_all.deb |
Debian | 999 | all | xen | < 4.16.2+90-g0d39a6d1ae-1 | xen_4.16.2+90-g0d39a6d1ae-1_all.deb |
Debian | 13 | all | xen | < 4.16.2+90-g0d39a6d1ae-1 | xen_4.16.2+90-g0d39a6d1ae-1_all.deb |