7.8
CVE-2019-19448
- EPSS 0.2%
- Published 08.12.2019 02:15:09
- Last modified 21.11.2024 04:34:45
- Source cve@mitre.org
- Teams watchlist Login
- Open Login
In the Linux kernel 5.0.21 and 5.3.11, mounting a crafted btrfs filesystem image, performing some operations, and then making a syncfs system call can lead to a use-after-free in try_merge_free_space in fs/btrfs/free-space-cache.c because the pointer to a left data structure can be the same as the pointer to a right data structure.
Data is provided by the National Vulnerability Database (NVD)
Linux ≫ Linux Kernel Version >= 2.6.31 < 4.4.233
Linux ≫ Linux Kernel Version >= 4.5.0 < 4.9.233
Linux ≫ Linux Kernel Version >= 4.10 < 4.14.194
Linux ≫ Linux Kernel Version >= 4.15 < 4.19.141
Linux ≫ Linux Kernel Version >= 4.20 < 5.4.60
Linux ≫ Linux Kernel Version >= 5.5.0 < 5.7.17
Linux ≫ Linux Kernel Version >= 5.8 < 5.8.3
Debian ≫ Debian Linux Version9.0
Canonical ≫ Ubuntu Linux Version14.04 SwEditionesm
Canonical ≫ Ubuntu Linux Version16.04 SwEditionesm
Canonical ≫ Ubuntu Linux Version18.04 SwEditionlts
Netapp ≫ Active Iq Unified Manager Version- SwPlatformvmware_vsphere
Netapp ≫ Cloud Backup Version-
Netapp ≫ Data Availability Services Version-
Netapp ≫ Hci Management Node Version-
Netapp ≫ Steelstore Cloud Integrated Storage Version-
Netapp ≫ A700s Firmware Version-
Netapp ≫ Fas 8300 Firmware Version-
Netapp ≫ Fas 8700 Firmware Version-
Netapp ≫ Fas A400 Firmware Version-
Netapp ≫ Aff 8300 Firmware Version-
Netapp ≫ Aff 8700 Firmware Version-
Netapp ≫ Aff A400 Firmware Version-
Netapp ≫ H610s Firmware Version-
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
| Type | Source | Score | Percentile |
|---|---|---|---|
| EPSS | FIRST.org | 0.2% | 0.422 |
| Source | Base Score | Exploit Score | Impact Score | Vector string |
|---|---|---|---|---|
| nvd@nist.gov | 7.8 | 1.8 | 5.9 |
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
|
| nvd@nist.gov | 6.8 | 8.6 | 6.4 |
AV:N/AC:M/Au:N/C:P/I:P/A:P
|
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.