Vulnerabilities > Linux > Linux Kernel > 5.15.0.58
DATE | CVE | VULNERABILITY TITLE | RISK |
---|---|---|---|
2023-08-07 | CVE-2023-4194 | Incorrect Authorization vulnerability in multiple products A flaw was found in the Linux kernel's TUN/TAP functionality. | 5.5 |
2023-07-24 | CVE-2023-33951 | Improper Locking vulnerability in multiple products A race condition vulnerability was found in the vmwgfx driver in the Linux kernel. | 5.3 |
2023-07-24 | CVE-2023-33952 | Double Free vulnerability in multiple products A double-free vulnerability was found in handling vmw_buffer_object objects in the vmwgfx driver in the Linux kernel. | 6.7 |
2023-07-24 | CVE-2023-3567 | Use After Free vulnerability in multiple products A use-after-free flaw was found in vcs_read in drivers/tty/vt/vc_screen.c in vc_screen in the Linux Kernel. | 7.1 |
2023-07-24 | CVE-2023-3812 | Use After Free vulnerability in multiple products An out-of-bounds memory access flaw was found in the Linux kernel’s TUN/TAP device driver functionality in how a user generates a malicious (too big) networking packet when napi frags is enabled. | 7.8 |
2023-07-06 | CVE-2023-37453 | Out-of-bounds Read vulnerability in Linux Kernel An issue was discovered in the USB subsystem in the Linux kernel through 6.4.2. | 4.6 |
2023-07-06 | CVE-2023-37454 | Use After Free vulnerability in Linux Kernel An issue was discovered in the Linux kernel through 6.4.2. | 5.5 |
2023-06-28 | CVE-2023-3390 | Use After Free vulnerability in multiple products A use-after-free vulnerability was found in the Linux kernel's netfilter subsystem in net/netfilter/nf_tables_api.c. Mishandled error handling with NFT_MSG_NEWRULE makes it possible to use a dangling pointer in the same transaction causing a use-after-free vulnerability. | 7.8 |
2023-05-31 | CVE-2023-34256 | Out-of-bounds Read vulnerability in multiple products An issue was discovered in the Linux kernel before 6.3.3. | 5.5 |
2023-03-01 | CVE-2023-23005 | NULL Pointer Dereference vulnerability in multiple products In the Linux kernel before 6.2, mm/memory-tiers.c misinterprets the alloc_memory_type return value (expects it to be NULL in the error case, whereas it is actually an error pointer). | 5.5 |