8.8
CVE-2020-29569
- EPSS 0.07%
- Veröffentlicht 15.12.2020 17:15:14
- Zuletzt bearbeitet 21.11.2024 05:24:13
- Quelle cve@mitre.org
- Teams Watchlist Login
- Unerledigt Login
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.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 4.1.44 < 4.2
Linux ≫ Linux Kernel Version >= 4.4.80 < 4.4.254
Linux ≫ Linux Kernel Version >= 4.9.36 < 4.9.249
Linux ≫ Linux Kernel Version >= 4.11.9 < 4.12
Linux ≫ Linux Kernel Version >= 4.12 < 4.14.213
Linux ≫ Linux Kernel Version >= 4.15 < 4.19.164
Linux ≫ Linux Kernel Version >= 4.20 < 5.4.86
Linux ≫ Linux Kernel Version >= 5.5 < 5.10.4
Netapp ≫ Hci Compute Node Bios Version-
Netapp ≫ Solidfire & Hci Management Node Version-
Netapp ≫ Solidfire & Hci Storage Node Version-
Debian ≫ Debian Linux Version9.0
Debian ≫ Debian Linux Version10.0
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Typ | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.07% | 0.218 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 8.8 | 2 | 6 |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
|
nvd@nist.gov | 7.2 | 3.9 | 10 |
AV:L/AC:L/Au:N/C:C/I:C/A:C
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.