rpm package
suse/kernel-source-rt&distro=SUSE Linux Enterprise Micro 5.5
pkg:rpm/suse/kernel-source-rt&distro=SUSE%20Linux%20Enterprise%20Micro%205.5
Vulnerabilities (4,559)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-48763 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Forcibly leave nested virt when SMM state is toggled Forcibly leave nested virtualization operation if userspace toggles SMM state via KVM_SET_VCPU_EVENTS or KVM_SYNC_X86_EVENTS. If userspace forces | ||
| CVE-2022-48761 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: usb: xhci-plat: fix crash when suspend if remote wake enable Crashed at i.mx8qm platform when suspend if enable remote wakeup Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP Modules linke | ||
| CVE-2022-48760 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix hang in usb_kill_urb by adding memory barriers The syzbot fuzzer has identified a bug in which processes hang waiting for usb_kill_urb() to return. It turns out the issue is not unlinking the UR | ||
| CVE-2022-48759 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev struct rpmsg_ctrldev contains a struct cdev. The current code frees the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev i | ||
| CVE-2022-48758 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() The bnx2fc_destroy() functions are removing the interface before calling destroy_work. This results multiple WARNings from sysfs_remo | ||
| CVE-2022-48756 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable The function performs a check on the "phy" input parameter, however, it is used before the check. Initialize the "dev" variable after the sanity check | ||
| CVE-2022-48755 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06 Johan reported the below crash with test_bpf on ppc64 e5500: test_bpf: #296 ALU_END_FROM_LE 64: 0x0123456789abcdef -> 0x67452301 jited:1 | ||
| CVE-2022-48754 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: phylib: fix potential use-after-free Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call to phy_device_reset(phydev) after the put_device() call in phy_detach(). The comment before the put | ||
| CVE-2022-48753 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: block: fix memory leak in disk_register_independent_access_ranges kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error, | ||
| CVE-2022-48752 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending Running selftest with CONFIG_PPC_IRQ_SOFT_MASK_DEBUG enabled in kernel triggered below warning: [ 172.851380] --------- | ||
| CVE-2022-48751 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/smc: Transitional solution for clcsock race issue We encountered a crash in smc_setsockopt() and it is caused by accessing smc->clcsock after clcsock was released. BUG: kernel NULL pointer dereference, ad | ||
| CVE-2022-48749 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc The function performs a check on the "ctx" input parameter, however, it is used before the check. Initialize the "base" variable after the sanity chec | ||
| CVE-2022-48748 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: bridge: vlan: fix memory leak in __allowed_ingress When using per-vlan state, if vlan snooping and stats are disabled, untagged or priority-tagged ingress frame will go to check pvid state. If the port sta | ||
| CVE-2022-48747 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: block: Fix wrong offset in bio_truncate() bio_truncate() clears the buffer outside of last block of bdev, however current bio_truncate() is using the wrong offset of page. So it can return the uninitialized dat | ||
| CVE-2022-48746 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix handling of wrong devices during bond netevent Current implementation of bond netevent handler only check if the handled netdev is VF representor and it missing a check if the VF representor is o | ||
| CVE-2022-48745 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Use del_timer_sync in fw reset flow of halting poll Substitute del_timer() with del_timer_sync() in fw reset polling deactivation flow, in order to prevent a race condition which occurs when del_timer | ||
| CVE-2022-48744 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid field-overflowing memcpy() In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for memcpy(), memmove(), and memset(), avoid intentionally writing across | ||
| CVE-2022-48743 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: amd-xgbe: Fix skb data length underflow There will be BUG_ON() triggered in include/linux/skbuff.h leading to intermittent kernel panic, when the skb length underflow is detected. Fix this by dropping the | ||
| CVE-2022-48742 | — | < 5.14.21-150500.13.82.1 | 5.14.21-150500.13.82.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() While looking at one unrelated syzbot bug, I found the replay logic in __rtnl_newlink() to potentially trigger use-after-free. It is better | ||
| CVE-2022-48740 | — | < 5.14.21-150500.13.61.1 | 5.14.21-150500.13.61.1 | Jun 20, 2024 | In the Linux kernel, the following vulnerability has been resolved: selinux: fix double free of cond_list on error paths On error path from cond_read_list() and duplicate_policydb_cond_list() the cond_list_destroy() gets called a second time in caller functions, resulting in NU |
- CVE-2022-48763Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Forcibly leave nested virt when SMM state is toggled Forcibly leave nested virtualization operation if userspace toggles SMM state via KVM_SET_VCPU_EVENTS or KVM_SYNC_X86_EVENTS. If userspace forces
- CVE-2022-48761Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: usb: xhci-plat: fix crash when suspend if remote wake enable Crashed at i.mx8qm platform when suspend if enable remote wakeup Internal error: synchronous external abort: 96000210 [#1] PREEMPT SMP Modules linke
- CVE-2022-48760Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: USB: core: Fix hang in usb_kill_urb by adding memory barriers The syzbot fuzzer has identified a bug in which processes hang waiting for usb_kill_urb() to return. It turns out the issue is not unlinking the UR
- CVE-2022-48759Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev struct rpmsg_ctrldev contains a struct cdev. The current code frees the rpmsg_ctrldev struct in rpmsg_ctrldev_release_device(), but the cdev i
- CVE-2022-48758Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put() The bnx2fc_destroy() functions are removing the interface before calling destroy_work. This results multiple WARNings from sysfs_remo
- CVE-2022-48756Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable The function performs a check on the "phy" input parameter, however, it is used before the check. Initialize the "dev" variable after the sanity check
- CVE-2022-48755Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: powerpc64/bpf: Limit 'ldbrx' to processors compliant with ISA v2.06 Johan reported the below crash with test_bpf on ppc64 e5500: test_bpf: #296 ALU_END_FROM_LE 64: 0x0123456789abcdef -> 0x67452301 jited:1
- CVE-2022-48754Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: phylib: fix potential use-after-free Commit bafbdd527d56 ("phylib: Add device reset GPIO support") added call to phy_device_reset(phydev) after the put_device() call in phy_detach(). The comment before the put
- CVE-2022-48753Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: block: fix memory leak in disk_register_independent_access_ranges kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error,
- CVE-2022-48752Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: powerpc/perf: Fix power_pmu_disable to call clear_pmi_irq_pending only if PMI is pending Running selftest with CONFIG_PPC_IRQ_SOFT_MASK_DEBUG enabled in kernel triggered below warning: [ 172.851380] ---------
- CVE-2022-48751Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net/smc: Transitional solution for clcsock race issue We encountered a crash in smc_setsockopt() and it is caused by accessing smc->clcsock after clcsock was released. BUG: kernel NULL pointer dereference, ad
- CVE-2022-48749Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: drm/msm/dpu: invalid parameter check in dpu_setup_dspp_pcc The function performs a check on the "ctx" input parameter, however, it is used before the check. Initialize the "base" variable after the sanity chec
- CVE-2022-48748Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net: bridge: vlan: fix memory leak in __allowed_ingress When using per-vlan state, if vlan snooping and stats are disabled, untagged or priority-tagged ingress frame will go to check pvid state. If the port sta
- CVE-2022-48747Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: block: Fix wrong offset in bio_truncate() bio_truncate() clears the buffer outside of last block of bdev, however current bio_truncate() is using the wrong offset of page. So it can return the uninitialized dat
- CVE-2022-48746Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix handling of wrong devices during bond netevent Current implementation of bond netevent handler only check if the handled netdev is VF representor and it missing a check if the VF representor is o
- CVE-2022-48745Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Use del_timer_sync in fw reset flow of halting poll Substitute del_timer() with del_timer_sync() in fw reset polling deactivation flow, in order to prevent a race condition which occurs when del_timer
- CVE-2022-48744Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Avoid field-overflowing memcpy() In preparation for FORTIFY_SOURCE performing compile-time and run-time field bounds checking for memcpy(), memmove(), and memset(), avoid intentionally writing across
- CVE-2022-48743Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: net: amd-xgbe: Fix skb data length underflow There will be BUG_ON() triggered in include/linux/skbuff.h leading to intermittent kernel panic, when the skb length underflow is detected. Fix this by dropping the
- CVE-2022-48742Jun 20, 2024affected < 5.14.21-150500.13.82.1fixed 5.14.21-150500.13.82.1
In the Linux kernel, the following vulnerability has been resolved: rtnetlink: make sure to refresh master_dev/m_ops in __rtnl_newlink() While looking at one unrelated syzbot bug, I found the replay logic in __rtnl_newlink() to potentially trigger use-after-free. It is better
- CVE-2022-48740Jun 20, 2024affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1
In the Linux kernel, the following vulnerability has been resolved: selinux: fix double free of cond_list on error paths On error path from cond_read_list() and duplicate_policydb_cond_list() the cond_list_destroy() gets called a second time in caller functions, resulting in NU
Page 162 of 228