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
Link | Resource |
---|---|
https://lists.debian.org/debian-lts-announce/2021/02/msg00018.html | Mailing List Third Party Advisory |
https://lists.debian.org/debian-lts-announce/2021/03/msg00010.html | Mailing List Third Party Advisory |
https://security.gentoo.org/glsa/202107-30 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20210205-0001/ | Third Party Advisory |
https://www.debian.org/security/2021/dsa-4843 | Third Party Advisory |
https://xenbits.xenproject.org/xsa/advisory-350.html | Patch Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-12-15T17:00:36
Updated: 2021-07-12T04:06:41
Reserved: 2020-12-04T00:00:00
Link: CVE-2020-29569
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-12-15T17:15:14.707
Modified: 2023-01-19T15:53:51.257
Link: CVE-2020-29569
JSON object: View
Redhat Information
No data.
CWE