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://xenbits.xenproject.org/xsa/advisory-350.html | Patch Vendor Advisory |
https://www.debian.org/security/2021/dsa-4843 | Third Party Advisory |
https://security.netapp.com/advisory/ntap-20210205-0001/ | Third Party Advisory |
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 |
Configurations
Configuration 1 (hide)
|
Configuration 2 (hide)
|
Configuration 3 (hide)
AND |
|
Configuration 4 (hide)
|
Configuration 5 (hide)
|
Information
Published : 2020-12-15 09:15
Updated : 2023-01-19 07:53
NVD link : CVE-2020-29569
Mitre link : CVE-2020-29569
JSON object : View
CWE
CWE-416
Use After Free
Products Affected
netapp
- hci_compute_node
- solidfire_\&_hci_storage_node
- solidfire_\&_hci_management_node
- hci_compute_node_bios
xen
- xen
linux
- linux_kernel
debian
- debian_linux