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.
6.11.0-8.84.13.0-16.194.13.0-17.204.13.0-25.294.13.0-32.354.15.0-10.114.15.0-101.1024.15.0-106.1074.15.0-108.1094.15.0-109.1104.15.0-111.112+58 more4.15.0-136.1406.5.0-9.95.3.0-18.195.3.0-24.265.4.0-18.225.4.0-21.255.4.0-24.285.4.0-25.295.4.0-26.305.4.0-28.325.4.0-29.335.4.0-31.35+20 more5.4.0-66.744.2.0-16.194.2.0-17.214.2.0-19.234.3.0-1.104.3.0-2.114.3.0-5.164.3.0-6.174.3.0-7.184.4.0-10.254.4.0-101.124+113 more4.4.0-204.2365.13.0-19.193.11.0-12.195.13.0-1005.64.4.0-1001.104.4.0-1003.124.4.0-1004.134.4.0-1007.164.4.0-1009.184.4.0-1011.204.4.0-1012.214.4.0-1013.224.4.0-1016.254.4.0-1017.26+69 more4.4.0-1123.1374.4.0-1002.24.4.0-1003.34.4.0-1005.54.4.0-1006.64.4.0-1009.94.4.0-1010.104.4.0-1011.114.4.0-1012.124.4.0-1014.144.4.0-1016.16+42 more4.4.0-1087.91Exploitability
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