rpm package
suse/kernel-source-rt&distro=SUSE Linux Enterprise Micro 5.2
pkg:rpm/suse/kernel-source-rt&distro=SUSE%20Linux%20Enterprise%20Micro%205.2
Vulnerabilities (1,394)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-47280 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv->master prior to locking the device's master mutex. An example can b | ||
| CVE-2021-47276 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: ftrace: Do not blindly read the ip address in ftrace_bug() It was reported that a bug on arm64 caused a bad ip address to be used for updating into a nop in ftrace_init(), but the error path (rightfully) return | ||
| CVE-2021-47275 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: bcache: avoid oversized read request in cache missing code path In the cache missing code path of cached device, if a proper location from the internal B+ tree is matched for a cache miss range, function cached | ||
| CVE-2021-47274 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: tracing: Correct the length check which causes memory corruption We've suffered from severe kernel crashes due to memory corruption on our production environment, like, Call Trace: [1640542.554277] general pro | ||
| CVE-2021-47270 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadgets null ptr deref on 10gbps cabling. This avoids a null pointer dereference in f_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm} by simply reusing the 5gbps config for 10 | ||
| CVE-2021-47269 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: ep0: fix NULL pointer exception There is no validation of the index from dwc3_wIndex_to_dep() and we might be referring a non-existing ep and trigger a NULL pointer exception. In certain configuratio | ||
| CVE-2021-47267 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadget panics on 10gbps cabling usb_assign_descriptors() is called with 5 parameters, the last 4 of which are the usb_descriptor_header for: full-speed (USB1.1 - 12Mbps [including USB1.0 low- | ||
| CVE-2021-47265 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: RDMA: Verify port when creating flow rule Validate port value provided by the user and with that remove no longer needed validation by the driver. The missing check in the mlx5_ib driver could cause to the bel | ||
| CVE-2021-47263 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: gpio: wcd934x: Fix shift-out-of-bounds error bit-mask for pins 0 to 4 is BIT(0) to BIT(4) however we ended up with BIT(n - 1) which is not right, and this was caught by below usban check UBSAN: shift-out-of-bo | ||
| CVE-2021-47261 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix initializing CQ fragments buffer The function init_cq_frag_buf() can be called to initialize the current CQ fragments buffer cq->buf, or the temporary cq->resize_buf that is filled during CQ resize | ||
| CVE-2021-47260 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a potential NULL dereference in nfs_get_client() None of the callers are expecting NULL returns from nfs_get_client() so this code will lead to an Oops. It's better to return an error pointer. I expe | ||
| CVE-2021-47259 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: NFS: Fix use-after-free in nfs4_init_client() KASAN reports a use-after-free when attempting to mount two different exports through two different NICs that belong to the same server. Olga was able to hit this | ||
| CVE-2021-47258 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix error handling of scsi_host_alloc() After device is initialized via device_initialize(), or its name is set via dev_set_name(), the device has to be freed via put_device(). Otherwise device nam | ||
| CVE-2021-47255 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: kvm: LAPIC: Restore guard to prevent illegal APIC register access Per the SDM, "any access that touches bytes 4 through 15 of an APIC register may cause undefined behavior and must not be executed." Worse, such | ||
| CVE-2021-47254 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix use-after-free in gfs2_glock_shrink_scan The GLF_LRU flag is checked under lru_lock in gfs2_glock_remove_from_lru() to remove the glock from the lru list in __gfs2_glock_put(). On the shrink scan pat | ||
| CVE-2021-47253 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential memory leak in DMUB hw_init [Why] On resume we perform DMUB hw_init which allocates memory: dm_resume->dm_dmub_hw_init->dc_dmub_srv_create->kzalloc That results in memory leak in | ||
| CVE-2021-47252 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: batman-adv: Avoid WARN_ON timing related checks The soft/batadv interface for a queued OGM can be changed during the time the OGM was queued for transmission and when the OGM is actually transmitted by the work | ||
| CVE-2021-47248 | — | < 5.3.18-150300.205.1 | 5.3.18-150300.205.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: udp: fix race between close() and udp_abort() Kaustubh reported and diagnosed a panic in udp_lib_lookup(). The root cause is udp_abort() racing with close(). Both racing functions acquire the socket lock, but u | ||
| CVE-2021-47247 | — | < 5.3.18-150300.175.1 | 5.3.18-150300.175.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free of encap entry in neigh update handler Function mlx5e_rep_neigh_update() wasn't updated to accommodate rtnl lock removal from TC filter update path and properly handle concurrent e | ||
| CVE-2021-47246 | — | < 5.3.18-150300.172.1 | 5.3.18-150300.172.1 | May 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix page reclaim for dead peer hairpin When adding a hairpin flow, a firmware-side send queue is created for the peer net device, which claims some host memory pages for its internal ring buffer. If |
- CVE-2021-47280May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: drm: Fix use-after-free read in drm_getunique() There is a time-of-check-to-time-of-use error in drm_getunique() due to retrieving file_priv->master prior to locking the device's master mutex. An example can b
- CVE-2021-47276May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: ftrace: Do not blindly read the ip address in ftrace_bug() It was reported that a bug on arm64 caused a bad ip address to be used for updating into a nop in ftrace_init(), but the error path (rightfully) return
- CVE-2021-47275May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: bcache: avoid oversized read request in cache missing code path In the cache missing code path of cached device, if a proper location from the internal B+ tree is matched for a cache miss range, function cached
- CVE-2021-47274May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Correct the length check which causes memory corruption We've suffered from severe kernel crashes due to memory corruption on our production environment, like, Call Trace: [1640542.554277] general pro
- CVE-2021-47270May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadgets null ptr deref on 10gbps cabling. This avoids a null pointer dereference in f_{ecm,eem,hid,loopback,printer,rndis,serial,sourcesink,subset,tcm} by simply reusing the 5gbps config for 10
- CVE-2021-47269May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: ep0: fix NULL pointer exception There is no validation of the index from dwc3_wIndex_to_dep() and we might be referring a non-existing ep and trigger a NULL pointer exception. In certain configuratio
- CVE-2021-47267May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: usb: fix various gadget panics on 10gbps cabling usb_assign_descriptors() is called with 5 parameters, the last 4 of which are the usb_descriptor_header for: full-speed (USB1.1 - 12Mbps [including USB1.0 low-
- CVE-2021-47265May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: RDMA: Verify port when creating flow rule Validate port value provided by the user and with that remove no longer needed validation by the driver. The missing check in the mlx5_ib driver could cause to the bel
- CVE-2021-47263May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: gpio: wcd934x: Fix shift-out-of-bounds error bit-mask for pins 0 to 4 is BIT(0) to BIT(4) however we ended up with BIT(n - 1) which is not right, and this was caught by below usban check UBSAN: shift-out-of-bo
- CVE-2021-47261May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: IB/mlx5: Fix initializing CQ fragments buffer The function init_cq_frag_buf() can be called to initialize the current CQ fragments buffer cq->buf, or the temporary cq->resize_buf that is filled during CQ resize
- CVE-2021-47260May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: NFS: Fix a potential NULL dereference in nfs_get_client() None of the callers are expecting NULL returns from nfs_get_client() so this code will lead to an Oops. It's better to return an error pointer. I expe
- CVE-2021-47259May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: NFS: Fix use-after-free in nfs4_init_client() KASAN reports a use-after-free when attempting to mount two different exports through two different NICs that belong to the same server. Olga was able to hit this
- CVE-2021-47258May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: scsi: core: Fix error handling of scsi_host_alloc() After device is initialized via device_initialize(), or its name is set via dev_set_name(), the device has to be freed via put_device(). Otherwise device nam
- CVE-2021-47255May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: kvm: LAPIC: Restore guard to prevent illegal APIC register access Per the SDM, "any access that touches bytes 4 through 15 of an APIC register may cause undefined behavior and must not be executed." Worse, such
- CVE-2021-47254May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: gfs2: Fix use-after-free in gfs2_glock_shrink_scan The GLF_LRU flag is checked under lru_lock in gfs2_glock_remove_from_lru() to remove the glock from the lru list in __gfs2_glock_put(). On the shrink scan pat
- CVE-2021-47253May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential memory leak in DMUB hw_init [Why] On resume we perform DMUB hw_init which allocates memory: dm_resume->dm_dmub_hw_init->dc_dmub_srv_create->kzalloc That results in memory leak in
- CVE-2021-47252May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: batman-adv: Avoid WARN_ON timing related checks The soft/batadv interface for a queued OGM can be changed during the time the OGM was queued for transmission and when the OGM is actually transmitted by the work
- CVE-2021-47248May 21, 2024affected < 5.3.18-150300.205.1fixed 5.3.18-150300.205.1
In the Linux kernel, the following vulnerability has been resolved: udp: fix race between close() and udp_abort() Kaustubh reported and diagnosed a panic in udp_lib_lookup(). The root cause is udp_abort() racing with close(). Both racing functions acquire the socket lock, but u
- CVE-2021-47247May 21, 2024affected < 5.3.18-150300.175.1fixed 5.3.18-150300.175.1
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix use-after-free of encap entry in neigh update handler Function mlx5e_rep_neigh_update() wasn't updated to accommodate rtnl lock removal from TC filter update path and properly handle concurrent e
- CVE-2021-47246May 21, 2024affected < 5.3.18-150300.172.1fixed 5.3.18-150300.172.1
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix page reclaim for dead peer hairpin When adding a hairpin flow, a firmware-side send queue is created for the peer net device, which claims some host memory pages for its internal ring buffer. If
Page 52 of 70