9.3

CVE-2018-20836

An issue was discovered in the Linux kernel before 4.20. There is a race condition in smp_task_timedout() and smp_task_done() in drivers/scsi/libsas/sas_expander.c, leading to a use-after-free.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version < 3.16.72
Linux ≫ Linux Kernel Version >= 3.17 < 3.18.140
Linux ≫ Linux Kernel Version >= 3.19 < 4.4.180
Linux ≫ Linux Kernel Version >= 4.5 < 4.9.175
Linux ≫ Linux Kernel Version >= 4.10 < 4.14.118
Linux ≫ Linux Kernel Version >= 4.15 < 4.19.42
Canonical ≫ Ubuntu Linux Version 16.04 SwEdition esm
Debian ≫ Debian Linux Version 8.0
Debian ≫ Debian Linux Version 9.0
Debian ≫ Debian Linux Version 10.0
Netapp ≫ Active Iq Unified Manager SwPlatform vmware_vsphere Version >= 9.5
Netapp ≫ Snapprotect Version -
Netapp ≫ Storage Replication Adapter For Clustered Data Ontap Version - SwPlatform vmware_vsphere
Netapp ≫ Virtual Storage Console SwPlatform vmware_vsphere Version >= 7.2
Netapp ≫ Hci Compute Node Version -
Opensuse ≫ Leap Version 15.0
Opensuse ≫ Leap Version 15.1
VulnDex Vulnerability Enrichment
Diese Information steht angemeldeten Benutzern zur Verfügung. Login Login
Zu dieser CVE wurde keine Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 5.11% 0.913
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
NIST 8.1 2.2 5.9
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
NIST 9.3 8.6 10
AV:N/AC:M/Au:N/C:C/I:C/A:C
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.

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.

https://seclists.org/bugtraq/2019/Aug/18
Third Party Advisory
Mailing List
https://www.debian.org/security/2019/dsa-4497
Third Party Advisory
https://lists.debian.org/debian-lts-announce/2019/08/msg00017.html
Third Party Advisory
Mailing List
https://seclists.org/bugtraq/2019/Aug/13
Third Party Advisory
Mailing List
https://www.debian.org/security/2019/dsa-4495
Third Party Advisory
https://lists.debian.org/debian-lts-announce/2019/08/msg00016.html
Third Party Advisory
Mailing List
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00014.html
Third Party Advisory
Mailing List
http://lists.opensuse.org/opensuse-security-announce/2019-07/msg00025.html
Third Party Advisory
Mailing List
http://www.securityfocus.com/bid/108196
Third Party Advisory
VDB Entry
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b90cd6f2b905905fb42671009dc0e27c310a16ae
Patch
Vendor Advisory
https://github.com/torvalds/linux/commit/b90cd6f2b905905fb42671009dc0e27c310a16ae
Patch
Vendor Advisory
https://security.netapp.com/advisory/ntap-20190719-0003/
Third Party Advisory
https://support.f5.com/csp/article/K11225249
Third Party Advisory
https://usn.ubuntu.com/4076-1/
Third Party Advisory