Vulnerabilities > Linux > Linux Kernel > 4.14.109
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-01-15 | CVE-2023-6915 | NULL Pointer Dereference vulnerability in multiple products A Null pointer dereference problem was found in ida_free in lib/idr.c in the Linux Kernel. | 5.5 |
| 2024-01-12 | CVE-2022-48619 | Unspecified vulnerability in Linux Kernel An issue was discovered in drivers/input/input.c in the Linux kernel before 5.17.10. | 5.5 |
| 2024-01-11 | CVE-2023-51780 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 6.6.8. | 7.0 |
| 2024-01-11 | CVE-2023-51781 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 6.6.8. | 7.0 |
| 2024-01-11 | CVE-2023-51782 | Use After Free vulnerability in multiple products An issue was discovered in the Linux kernel before 6.6.8. | 7.0 |
| 2024-01-09 | CVE-2024-0340 | Unspecified vulnerability in Linux Kernel A vulnerability was found in vhost_new_msg in drivers/vhost/vhost.c in the Linux kernel, which does not properly initialize memory in messages passed between virtual guests and the host operating system in the vhost/vhost.c:vhost_new_msg() function. | 5.5 |
| 2024-01-08 | CVE-2022-2586 | Use After Free vulnerability in multiple products It was discovered that a nft object or expression could reference a nft set on a different nft table, leading to a use-after-free once that table was deleted. | 7.8 |
| 2024-01-08 | CVE-2022-2588 | Double Free vulnerability in multiple products It was discovered that the cls_route filter implementation in the Linux kernel would not remove an old filter from the hashtable before freeing it if its handle had the value 0. | 7.8 |
| 2024-01-08 | CVE-2022-2602 | Use After Free vulnerability in multiple products io_uring UAF, Unix SCM garbage collection | 7.0 |
| 2024-01-05 | CVE-2023-34324 | Resource Exhaustion vulnerability in multiple products Closing of an event channel in the Linux kernel can result in a deadlock. This happens when the close is being performed in parallel to an unrelated Xen console action and the handling of a Xen console interrupt in an unprivileged guest. The closing of an event channel is e.g. | 4.9 |