rpm package
opensuse/kernel-default&distro=openSUSE Leap 15.3
pkg:rpm/opensuse/kernel-default&distro=openSUSE%20Leap%2015.3
Vulnerabilities (340)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-0512 | — | < 5.3.18-59.13.1 | 5.3.18-59.13.1 | Jun 21, 2021 | In __hidinput_change_resolution_multipliers of hid-input.c, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Prod | ||
| CVE-2021-34693 | — | < 5.3.18-59.13.1 | 5.3.18-59.13.1 | Jun 14, 2021 | net/can/bcm.c in the Linux kernel through 5.12.10 allows local users to obtain sensitive information from kernel stack memory because parts of a data structure are uninitialized. | ||
| CVE-2021-0129 | — | < 5.3.18-59.10.1 | 5.3.18-59.10.1 | Jun 9, 2021 | Improper access control in BlueZ may allow an authenticated user to potentially enable information disclosure via adjacent access. | ||
| CVE-2021-3564 | — | < 4.12.14-197.105.1 | 4.12.14-197.105.1 | Jun 8, 2021 | A flaw double-free memory corruption in the Linux kernel HCI device initialization subsystem was found in the way user attach malicious HCI TTY Bluetooth device. A local user could use this flaw to crash the system. This flaw affects all the Linux kernel versions starting from 3. | ||
| CVE-2020-36386 | — | < 5.3.18-59.10.1 | 5.3.18-59.10.1 | Jun 7, 2021 | An issue was discovered in the Linux kernel before 5.8.1. net/bluetooth/hci_event.c has a slab out-of-bounds read in hci_extended_inquiry_result_evt, aka CID-51c19bf3d5cf. | ||
| CVE-2020-36385 | — | < 5.3.18-59.10.1 | 5.3.18-59.10.1 | Jun 7, 2021 | An issue was discovered in the Linux kernel before 5.10. drivers/infiniband/core/ucma.c has a use-after-free because the ctx is reached via the ctx_list in some ucma_migrate_id situations where ucma_close is called, aka CID-f5449e74802c. | ||
| CVE-2021-3491 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | Jun 4, 2021 | The io_uring subsystem in the Linux kernel allowed the MAX_RW_COUNT limit to be bypassed in the PROVIDE_BUFFERS operation, which led to negative values being usedin mem_rw when reading /proc//mem. This could be used to create a heap overflow leading to arbitrary code executi | ||
| CVE-2021-3490 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | Jun 4, 2021 | The eBPF ALU32 bounds tracking for bitwise ops (AND, OR and XOR) in the Linux kernel did not properly update 32-bit bounds, which could be turned into out of bounds reads and writes in the Linux kernel and therefore, arbitrary code execution. This issue was fixed via commit 049c4 | ||
| CVE-2021-3489 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | Jun 4, 2021 | The eBPF RINGBUF bpf_ringbuf_reserve() function in the Linux kernel did not check that the allocated size was smaller than the ringbuf size, allowing an attacker to perform out-of-bounds writes within the kernel and therefore, arbitrary code execution. This issue was fixed via co | ||
| CVE-2021-20292 | — | < 5.3.18-150300.59.68.1 | 5.3.18-150300.59.68.1 | May 28, 2021 | 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. The issue results from the lack of validating the existence of an object prior to performing operations on the obje | ||
| CVE-2021-33200 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 27, 2021 | kernel/bpf/verifier.c in the Linux kernel through 5.12.7 enforces incorrect limits for pointer arithmetic operations, aka CID-bb01a1bba579. This can be abused to perform out-of-bounds reads and writes in kernel memory, leading to local privilege escalation to root. In particular, | ||
| CVE-2020-27815 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 26, 2021 | A flaw was found in the JFS filesystem code in the Linux Kernel which allows a local attacker with the ability to set extended attributes to panic the system, causing memory corruption or escalating privileges. The highest threat from this vulnerability is to confidentiality, int | ||
| CVE-2020-25673 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 26, 2021 | A vulnerability was found in Linux kernel where non-blocking socket in llcp_sock_connect() leads to leak and eventually hanging-up the system. | ||
| CVE-2020-25671 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 26, 2021 | A vulnerability was found in Linux Kernel, where a refcount leak in llcp_sock_connect() causing use-after-free which might lead to privilege escalations. | ||
| CVE-2021-22543 | — | < 5.3.18-59.19.1 | 5.3.18-59.19.1 | May 26, 2021 | An issue was discovered in Linux: KVM through Improper handling of VM_IO|VM_PFNMAP vmas in KVM can bypass RO checks and can lead to pages being freed while still accessible by the VMM and guest. This allows users with the ability to start and control a VM to read/write random pag | ||
| CVE-2020-25670 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 26, 2021 | A vulnerability was found in Linux Kernel where refcount leak in llcp_sock_bind() causing use-after-free which might lead to privilege escalations. | ||
| CVE-2020-25672 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 25, 2021 | A memory leak vulnerability was found in Linux kernel in llcp_sock_connect | ||
| CVE-2020-26558 | — | < 5.3.18-59.10.1 | 5.3.18-59.10.1 | May 24, 2021 | Bluetooth LE and BR/EDR secure pairing in Bluetooth Core Specification 2.1 through 5.2 may permit a nearby man-in-the-middle attacker to identify the Passkey used during pairing (in the Passkey authentication procedure) by reflection of the public key and the authentication evide | ||
| CVE-2021-3483 | — | < 5.3.18-59.5.2 | 5.3.18-59.5.2 | May 17, 2021 | A flaw was found in the Nosy driver in the Linux kernel. This issue allows a device to be inserted twice into a doubly-linked list, leading to a use-after-free when one of these devices is removed. The highest threat from this vulnerability is to confidentiality, integrity, as we | ||
| CVE-2021-33033 | — | < 5.3.18-59.34.1 | 5.3.18-59.34.1 | May 14, 2021 | The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value. |
- CVE-2021-0512Jun 21, 2021affected < 5.3.18-59.13.1fixed 5.3.18-59.13.1
In __hidinput_change_resolution_multipliers of hid-input.c, there is a possible out of bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Prod
- CVE-2021-34693Jun 14, 2021affected < 5.3.18-59.13.1fixed 5.3.18-59.13.1
net/can/bcm.c in the Linux kernel through 5.12.10 allows local users to obtain sensitive information from kernel stack memory because parts of a data structure are uninitialized.
- CVE-2021-0129Jun 9, 2021affected < 5.3.18-59.10.1fixed 5.3.18-59.10.1
Improper access control in BlueZ may allow an authenticated user to potentially enable information disclosure via adjacent access.
- CVE-2021-3564Jun 8, 2021affected < 4.12.14-197.105.1fixed 4.12.14-197.105.1
A flaw double-free memory corruption in the Linux kernel HCI device initialization subsystem was found in the way user attach malicious HCI TTY Bluetooth device. A local user could use this flaw to crash the system. This flaw affects all the Linux kernel versions starting from 3.
- CVE-2020-36386Jun 7, 2021affected < 5.3.18-59.10.1fixed 5.3.18-59.10.1
An issue was discovered in the Linux kernel before 5.8.1. net/bluetooth/hci_event.c has a slab out-of-bounds read in hci_extended_inquiry_result_evt, aka CID-51c19bf3d5cf.
- CVE-2020-36385Jun 7, 2021affected < 5.3.18-59.10.1fixed 5.3.18-59.10.1
An issue was discovered in the Linux kernel before 5.10. drivers/infiniband/core/ucma.c has a use-after-free because the ctx is reached via the ctx_list in some ucma_migrate_id situations where ucma_close is called, aka CID-f5449e74802c.
- CVE-2021-3491Jun 4, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
The io_uring subsystem in the Linux kernel allowed the MAX_RW_COUNT limit to be bypassed in the PROVIDE_BUFFERS operation, which led to negative values being usedin mem_rw when reading /proc//mem. This could be used to create a heap overflow leading to arbitrary code executi
- CVE-2021-3490Jun 4, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
The eBPF ALU32 bounds tracking for bitwise ops (AND, OR and XOR) in the Linux kernel did not properly update 32-bit bounds, which could be turned into out of bounds reads and writes in the Linux kernel and therefore, arbitrary code execution. This issue was fixed via commit 049c4
- CVE-2021-3489Jun 4, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
The eBPF RINGBUF bpf_ringbuf_reserve() function in the Linux kernel did not check that the allocated size was smaller than the ringbuf size, allowing an attacker to perform out-of-bounds writes within the kernel and therefore, arbitrary code execution. This issue was fixed via co
- CVE-2021-20292May 28, 2021affected < 5.3.18-150300.59.68.1fixed 5.3.18-150300.59.68.1
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. The issue results from the lack of validating the existence of an object prior to performing operations on the obje
- CVE-2021-33200May 27, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
kernel/bpf/verifier.c in the Linux kernel through 5.12.7 enforces incorrect limits for pointer arithmetic operations, aka CID-bb01a1bba579. This can be abused to perform out-of-bounds reads and writes in kernel memory, leading to local privilege escalation to root. In particular,
- CVE-2020-27815May 26, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A flaw was found in the JFS filesystem code in the Linux Kernel which allows a local attacker with the ability to set extended attributes to panic the system, causing memory corruption or escalating privileges. The highest threat from this vulnerability is to confidentiality, int
- CVE-2020-25673May 26, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A vulnerability was found in Linux kernel where non-blocking socket in llcp_sock_connect() leads to leak and eventually hanging-up the system.
- CVE-2020-25671May 26, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A vulnerability was found in Linux Kernel, where a refcount leak in llcp_sock_connect() causing use-after-free which might lead to privilege escalations.
- CVE-2021-22543May 26, 2021affected < 5.3.18-59.19.1fixed 5.3.18-59.19.1
An issue was discovered in Linux: KVM through Improper handling of VM_IO|VM_PFNMAP vmas in KVM can bypass RO checks and can lead to pages being freed while still accessible by the VMM and guest. This allows users with the ability to start and control a VM to read/write random pag
- CVE-2020-25670May 26, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A vulnerability was found in Linux Kernel where refcount leak in llcp_sock_bind() causing use-after-free which might lead to privilege escalations.
- CVE-2020-25672May 25, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A memory leak vulnerability was found in Linux kernel in llcp_sock_connect
- CVE-2020-26558May 24, 2021affected < 5.3.18-59.10.1fixed 5.3.18-59.10.1
Bluetooth LE and BR/EDR secure pairing in Bluetooth Core Specification 2.1 through 5.2 may permit a nearby man-in-the-middle attacker to identify the Passkey used during pairing (in the Passkey authentication procedure) by reflection of the public key and the authentication evide
- CVE-2021-3483May 17, 2021affected < 5.3.18-59.5.2fixed 5.3.18-59.5.2
A flaw was found in the Nosy driver in the Linux kernel. This issue allows a device to be inserted twice into a doubly-linked list, leading to a use-after-free when one of these devices is removed. The highest threat from this vulnerability is to confidentiality, integrity, as we
- CVE-2021-33033May 14, 2021affected < 5.3.18-59.34.1fixed 5.3.18-59.34.1
The Linux kernel before 5.11.14 has a use-after-free in cipso_v4_genopt in net/ipv4/cipso_ipv4.c because the CIPSO and CALIPSO refcounting for the DOI definitions is mishandled, aka CID-ad5d07f4a9cd. This leads to writing an arbitrary value.
Page 14 of 17