Use After Free Affecting kernel-debuginfo-common-x86_64 package, versions <0:4.14.214-160.339.amzn2
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-AMZN2-KERNELDEBUGINFOCOMMONX8664-1693546
- published 27 Sep 2021
- disclosed 15 Dec 2020
Introduced: 15 Dec 2020
CVE-2020-29569 Open this link in a new tabHow to fix?
Upgrade Amazon-Linux:2 kernel-debuginfo-common-x86_64 to version 0:4.14.214-160.339.amzn2 or higher.
This issue was patched in ALAS2-2021-1588.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-debuginfo-common-x86_64 package and not the kernel-debuginfo-common-x86_64 package as distributed by Amazon-Linux.
See How to fix? for Amazon-Linux:2 relevant fixed versions and status.
An issue was discovered in the Linux kernel through 5.10.1, as used with Xen through 4.14.x. The Linux kernel PV block backend expects the kernel thread handler to reset ring->xenblkd to NULL when stopped. However, the handler may not have time to run if the frontend quickly toggles between the states connect and disconnect. As a consequence, the block backend may re-use a pointer after it was freed. A misbehaving guest can trigger a dom0 crash by continuously connecting / disconnecting a block frontend. Privilege escalation and information leaks cannot be ruled out. This only affects systems with a Linux blkback.
References
- https://security.netapp.com/advisory/ntap-20210205-0001/
- http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-29569
- https://www.debian.org/security/2021/dsa-4843
- https://security.gentoo.org/glsa/202107-30
- https://xenbits.xenproject.org/xsa/advisory-350.html
- https://lists.debian.org/debian-lts-announce/2021/02/msg00018.html
- https://lists.debian.org/debian-lts-announce/2021/03/msg00010.html