CVE-2021-28688

The fix for XSA-365 includes initialization of pointers such that subsequent cleanup code wouldnt 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.

Weakness

The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.

Affected Software

Potential Mitigations

• Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
• For example, in Java, if the programmer does not explicitly initialize a variable, then the code could produce a compile-time error (if the variable is local) or automatically initialize the variable to the default value for the variable’s type. In Perl, if explicit initialization is not performed, then a default value of undef is assigned, which is interpreted as 0, false, or an equivalent value depending on the context in which the variable is accessed.

Related Attack Patterns

• https://cwe.mitre.org/data/definitions/26.html
• https://cwe.mitre.org/data/definitions/29.html

References

• https://lists.debian.org/debian-lts-announce/2021/06/msg00019.html
• https://lists.debian.org/debian-lts-announce/2021/06/msg00020.html
• https://xenbits.xenproject.org/xsa/advisory-371.txt
• https://lists.debian.org/debian-lts-announce/2021/06/msg00019.html
• https://lists.debian.org/debian-lts-announce/2021/06/msg00020.html
• https://xenbits.xenproject.org/xsa/advisory-371.txt