Vulnerabilities > Linux > Linux Kernel > 4.1.38
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2021-06-07 | CVE-2018-25015 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 4.14.16. | 4.6 |
| 2021-06-07 | CVE-2019-25045 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 5.0.19. | 4.6 |
| 2021-06-07 | CVE-2020-36386 | Out-of-bounds Read vulnerability in Linux Kernel An issue was discovered in the Linux kernel before 5.8.1. | 5.6 |
| 2021-06-07 | CVE-2020-36385 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 5.10. | 7.8 |
| 2021-05-28 | CVE-2021-20239 | Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerability in multiple products A flaw was found in the Linux kernel in versions before 5.4.92 in the BPF protocol. | 3.3 |
| 2021-05-28 | CVE-2021-20292 | Use After Free vulnerability in multiple products There is a flaw reported in the Linux kernel in versions before 5.9 in drivers/gpu/drm/nouveau/nouveau_sgdma.c in nouveau_sgdma_create_ttm in Nouveau DRM subsystem. | 6.7 |
| 2021-05-27 | CVE-2020-10774 | Buffer Access with Incorrect Length Value vulnerability in Linux Kernel A memory disclosure flaw was found in the Linux kernel's versions before 4.18.0-193.el8 in the sysctl subsystem when reading the /proc/sys/kernel/rh_features file. | 2.1 |
| 2021-05-26 | CVE-2021-20177 | Out-of-bounds Read vulnerability in Linux Kernel A flaw was found in the Linux kernel's implementation of string matching within a packet. | 2.1 |
| 2021-05-26 | CVE-2020-25669 | Use After Free vulnerability in multiple products A vulnerability was found in the Linux Kernel where the function sunkbd_reinit having been scheduled by sunkbd_interrupt before sunkbd being freed. | 7.8 |
| 2021-05-26 | CVE-2020-25670 | Use After Free vulnerability in multiple products A vulnerability was found in Linux Kernel where refcount leak in llcp_sock_bind() causing use-after-free which might lead to privilege escalations. | 7.8 |