Memory leak in Xen 3.3 through 4.8.x allows guest OS users to cause a denial of service (ARM or x86 AMD host OS memory consumption) by continually rebooting, because certain cleanup is skipped if no pass-through device was ever assigned, aka XSA-207.
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Xen | Xen | 4.3.2 | 4.3.2 |
Xen | Xen | 4.6.0 | 4.6.0 |
Xen | Xen | 4.1.5 | 4.1.5 |
Xen | Xen | 4.2.2 | 4.2.2 |
Xen | Xen | 4.5.5 | 4.5.5 |
Xen | Xen | 4.2.3 | 4.2.3 |
Xen | Xen | 4.3.3 | 4.3.3 |
Xen | Xen | 3.4.0 | 3.4.0 |
Xen | Xen | 4.6.4 | 4.6.4 |
Xen | Xen | 4.3.0 | 4.3.0 |
Xen | Xen | 4.0.4 | 4.0.4 |
Xen | Xen | 4.0.2 | 4.0.2 |
Xen | Xen | 3.3.2 | 3.3.2 |
Xen | Xen | 4.7.1 | 4.7.1 |
Xen | Xen | 4.1.2 | 4.1.2 |
Xen | Xen | 4.5.2 | 4.5.2 |
Xen | Xen | 4.4.2 | 4.4.2 |
Xen | Xen | 4.4.4 | 4.4.4 |
Xen | Xen | 3.4.4 | 3.4.4 |
Xen | Xen | 4.0.0 | 4.0.0 |
Xen | Xen | 4.4.3 | 4.4.3 |
Xen | Xen | 4.4.0 | 4.4.0 |
Xen | Xen | 4.1.1 | 4.1.1 |
Xen | Xen | 4.6.1 | 4.6.1 |
Xen | Xen | 4.2.0 | 4.2.0 |
Xen | Xen | 4.1.0 | 4.1.0 |
Xen | Xen | 3.4.3 | 3.4.3 |
Xen | Xen | 4.8.0 | 4.8.0 |
Xen | Xen | 4.1.6 | 4.1.6 |
Xen | Xen | 4.5.3 | 4.5.3 |
Xen | Xen | 4.6.2 | 4.6.2 |
Xen | Xen | 4.2.5 | 4.2.5 |
Xen | Xen | 4.1.3 | 4.1.3 |
Xen | Xen | 4.1.6.1 | 4.1.6.1 |
Xen | Xen | 4.8.1 | 4.8.1 |
Xen | Xen | 4.3.4 | 4.3.4 |
Xen | Xen | 4.5.1 | 4.5.1 |
Xen | Xen | 3.3.1 | 3.3.1 |
Xen | Xen | 4.2.4 | 4.2.4 |
Xen | Xen | 3.4.2 | 3.4.2 |
Xen | Xen | 4.1.4 | 4.1.4 |
Xen | Xen | 3.4.1 | 3.4.1 |
Xen | Xen | 4.4.1 | 4.4.1 |
Xen | Xen | 4.3.1 | 4.3.1 |
Xen | Xen | 3.3.0 | 3.3.0 |
Xen | Xen | 4.2.1 | 4.2.1 |
Xen | Xen | 4.5.0 | 4.5.0 |
Xen | Xen | 4.4.0 | 4.4.0 |
Xen | Xen | 4.0.1 | 4.0.1 |
Xen | Xen | 4.0.3 | 4.0.3 |
Xen | Xen | 4.6.5 | 4.6.5 |