Vulnerabilities > Linux > Linux Kernel > 5.4.83
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 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. | 4.4 |
| 2020-05-09 | CVE-2020-12771 | Improper Locking vulnerability in multiple products An issue was discovered in the Linux kernel through 5.6.11. | 4.9 |
| 2020-05-09 | CVE-2020-12770 | An issue was discovered in the Linux kernel through 5.6.11. | 6.7 |
| 2020-05-09 | CVE-2020-12768 | Memory Leak vulnerability in multiple products An issue was discovered in the Linux kernel before 5.6. | 5.5 |
| 2020-05-09 | CVE-2019-20794 | Resource Exhaustion vulnerability in Linux Kernel An issue was discovered in the Linux kernel 4.18 through 5.6.11 when unprivileged user namespaces are allowed. | 4.7 |
| 2020-05-08 | CVE-2020-10690 | Use After Free vulnerability in multiple products There is a use-after-free in kernel versions before 5.5 due to a race condition between the release of ptp_clock and cdev while resource deallocation. | 6.4 |
| 2020-05-05 | CVE-2020-12656 | Memory Leak vulnerability in multiple products gss_mech_free in net/sunrpc/auth_gss/gss_mech_switch.c in the rpcsec_gss_krb5 implementation in the Linux kernel through 5.6.10 lacks certain domain_release calls, leading to a memory leak. | 5.5 |
| 2020-05-05 | CVE-2020-12655 | Infinite Loop vulnerability in Linux Kernel An issue was discovered in xfs_agf_verify in fs/xfs/libxfs/xfs_alloc.c in the Linux kernel through 5.6.10. | 5.5 |
| 2020-05-05 | CVE-2020-12653 | Out-of-bounds Write vulnerability in multiple products An issue was found in Linux kernel before 5.5.4. | 4.6 |
| 2020-04-12 | CVE-2020-11725 | Unspecified vulnerability in Linux Kernel snd_ctl_elem_add in sound/core/control.c in the Linux kernel through 5.6.3 has a count=info->owner line, which later affects a private_size*count multiplication for unspecified "interesting side effects." NOTE: kernel engineers dispute this finding, because it could be relevant only if new callers were added that were unfamiliar with the misuse of the info->owner field to represent data unrelated to the "owner" concept. | 7.8 |