Vulnerabilities > Linux > Linux Kernel > 4.19.130
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2020-06-18 | CVE-2020-14416 | Use After Free vulnerability in multiple products In the Linux kernel before 5.4.16, a race condition in tty->disc_data handling in the slip and slcan line discipline could lead to a use-after-free, aka CID-0ace17d56824. | 4.2 |
2020-06-03 | CVE-2019-20812 | Resource Exhaustion vulnerability in Linux Kernel An issue was discovered in the Linux kernel before 5.4.7. | 5.5 |
2020-06-03 | CVE-2019-20811 | An issue was discovered in the Linux kernel before 5.0.6. | 5.5 |
2020-06-03 | CVE-2019-20810 | Memory Leak vulnerability in multiple products go7007_snd_init in drivers/media/usb/go7007/snd-go7007.c in the Linux kernel before 5.6 does not call snd_card_free for a failure path, which causes a memory leak, aka CID-9453264ef586. | 5.5 |
2020-05-22 | CVE-2020-10711 | NULL Pointer Dereference vulnerability in multiple products A NULL pointer dereference flaw was found in the Linux kernel's SELinux subsystem in versions before 5.7. | 5.9 |
2020-05-18 | CVE-2020-13143 | Out-of-bounds Read vulnerability in multiple products gadget_dev_desc_UDC_store in drivers/usb/gadget/configfs.c in the Linux kernel 3.16 through 5.6.13 relies on kstrdup without considering the possibility of an internal '\0' value, which allows attackers to trigger an out-of-bounds read, aka CID-15753588bcd4. | 6.5 |
2020-05-15 | CVE-2020-12888 | Improper Handling of Exceptional Conditions vulnerability in multiple products The VFIO PCI driver in the Linux kernel through 5.6.13 mishandles attempts to access disabled memory space. | 5.3 |
2020-05-12 | CVE-2020-12826 | Integer Overflow or Wraparound vulnerability in multiple products A signal access-control issue was discovered in the Linux kernel before 5.6.5, aka CID-7395ea4e65c2. | 5.3 |
2020-05-09 | CVE-2020-12771 | Improper Locking vulnerability in multiple products An issue was discovered in the Linux kernel through 5.6.11. | 5.5 |
2020-05-09 | CVE-2020-12770 | An issue was discovered in the Linux kernel through 5.6.11. | 6.7 |