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.
4.4.0-204.2364.4.0-1123.1374.15.0-1094.101~16.04.14.15.0-1108.120~16.04.14.15.0-1093.106~16.04.14.15.0-136.140~16.04.14.10.0-14.16~16.04.14.10.0-19.21~16.04.14.10.0-20.22~16.04.14.10.0-21.23~16.04.14.10.0-22.24~16.04.14.10.0-24.28~16.04.14.10.0-26.30~16.04.14.11.0-13.19~16.04.14.11.0-14.20~16.04.14.13.0-16.19~16.04.3+13 more4.4.0-1089.984.15.0-1065.73~16.04.14.4.0-1147.157Exploitability
AV:LAC:LPR:LUI:NScope
S:CImpact
C:HI:HA:HCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H