In grub2 versions before 2.06 the grub memory allocator doesn't check for possible arithmetic overflows on the requested allocation size. This leads the function to return invalid memory allocations which can be further used to cause possible integrity, confidentiality and availability impacts during the boot process.
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
| Link | Tags |
|---|---|
| https://bugzilla.redhat.com/show_bug.cgi?id=1852009 | issue tracking third party advisory |
| http://www.openwall.com/lists/oss-security/2020/07/29/3 | third party advisory mailing list |
| https://security.netapp.com/advisory/ntap-20200731-0008/ | third party advisory |
| https://usn.ubuntu.com/4432-1/ | third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00017.html | mailing list third party advisory vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-08/msg00016.html | mailing list third party advisory vendor advisory |
| https://security.gentoo.org/glsa/202104-05 | third party advisory vendor advisory |
| http://www.openwall.com/lists/oss-security/2021/09/17/2 | third party advisory mailing list |
| http://www.openwall.com/lists/oss-security/2021/09/17/4 | third party advisory mailing list |
| http://www.openwall.com/lists/oss-security/2021/09/21/1 | third party advisory mailing list |