rpm package
suse/kernel-default&distro=SUSE Linux Enterprise Server 15 SP3-LTSS
pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP3-LTSS
Vulnerabilities (1,501)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2022-49022 | Hig | 8.1 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: wifi: mac8021: fix possible oob access in ieee80211_get_rate_duration Fix possible out-of-bound access in ieee80211_get_rate_duration routine as reported by the following UBSAN report: UBSAN: array-index-out-o | |
| CVE-2022-49021 | Med | 5.5 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PRE | |
| CVE-2022-49019 | Med | 5.5 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: ethernet: nixge: fix NULL dereference In function nixge_hw_dma_bd_release() dereference of NULL pointer priv->rx_bd_v is possible for the case of its allocation failure in nixge_hw_dma_bd_init(). Move for | |
| CVE-2022-49015 | Hig | 8.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: hsr: Fix potential use-after-free The skb is delivered to netif_rx() which may free it, after calling this, dereferencing skb may trigger use-after-free. | |
| CVE-2022-49014 | Hig | 7.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: tun: Fix use-after-free in tun_detach() syzbot reported use-after-free in tun_detach() [1]. This causes call trace like below: ================================================================== BUG: KASA | |
| CVE-2022-49011 | Med | 5.5 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decremen | |
| CVE-2022-49010 | Med | 5.5 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Check for null before removing sysfs attrs If coretemp_add_core() gets an error then pdata->core_data[indx] is already NULL and has been kfreed. Don't pass that to sysfs_remove_group() as that | |
| CVE-2022-49006 | Hig | 7.8 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: tracing: Free buffers when a used dynamic event is removed After 65536 dynamic events have been added and removed, the "type" field of the event then uses the first type number that is available (not currently | |
| CVE-2022-49003 | Cri | 9.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: nvme: fix SRCU protection of nvme_ns_head list Walking the nvme_ns_head siblings list is protected by the head's srcu in nvme_ns_head_submit_bio() but not nvme_mpath_revalidate_paths(). Removing namespaces from | |
| CVE-2022-48999 | Hig | 7.1 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference Gwangun Jung reported a slab-out-of-bounds access in fib_nh_match: fib_nh_match+0xf98/0x1130 linux-6.0-rc7/net/ipv4/fib_ | |
| CVE-2022-48991 | Hig | 8.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which are | |
| CVE-2022-48988 | Hig | 7.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't b | |
| CVE-2022-48985 | Cri | 9.8 | < 5.3.18-150300.59.185.1 | 5.3.18-150300.59.185.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix race on per-CQ variable napi work_done After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be cleared, and another CPU can start napi thread and access per-CQ variable, cq->work_don | |
| CVE-2022-48970 | Med | 5.5 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: af_unix: Get user_ns from in_skb in unix_diag_get_exact(). Wei Chen reported a NULL deref in sk_user_ns() [0][1], and Paolo diagnosed the root cause: in unix_diag_get_exact(), the newly allocated skb does not h | |
| CVE-2022-48967 | Hig | 8.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: NFC: nci: Bounds check struct nfc_target arrays While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported: memcpy: detected field-spanning write (size 129) of single field "target->sensf_res" at net/nf | |
| CVE-2022-48962 | Hig | 8.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free. | |
| CVE-2022-48960 | Hig | 8.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free. | |
| CVE-2022-48956 | Hig | 7.8 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: ipv6: avoid use-after-free in ip6_fragment() Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers. It seems to not be always true, at least for UDP stack. syzbot reported: BUG: KASAN: use | |
| CVE-2022-48947 | Med | 5.5 | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix u8 overflow By keep sending L2CAP_CONF_REQ packets, chan->num_conf_rsp increases multiple times and eventually it will wrap around the maximum number (i.e., 255). This patch prevents this | |
| CVE-2024-49995 | — | < 5.3.18-150300.59.182.1 | 5.3.18-150300.59.182.1 | Oct 21, 2024 | Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority. |
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: wifi: mac8021: fix possible oob access in ieee80211_get_rate_duration Fix possible out-of-bound access in ieee80211_get_rate_duration routine as reported by the following UBSAN report: UBSAN: array-index-out-o
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: net: phy: fix null-ptr-deref while probe() failed I got a null-ptr-deref report as following when doing fault injection test: BUG: kernel NULL pointer dereference, address: 0000000000000058 Oops: 0000 [#1] PRE
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: net: ethernet: nixge: fix NULL dereference In function nixge_hw_dma_bd_release() dereference of NULL pointer priv->rx_bd_v is possible for the case of its allocation failure in nixge_hw_dma_bd_init(). Move for
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: net: hsr: Fix potential use-after-free The skb is delivered to netif_rx() which may free it, after calling this, dereferencing skb may trigger use-after-free.
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: net: tun: Fix use-after-free in tun_detach() syzbot reported use-after-free in tun_detach() [1]. This causes call trace like below: ================================================================== BUG: KASA
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) fix pci device refcount leak in nv1a_ram_new() As comment of pci_get_domain_bus_and_slot() says, it returns a pci device with refcount increment, when finish using it, the caller must decremen
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: hwmon: (coretemp) Check for null before removing sysfs attrs If coretemp_add_core() gets an error then pdata->core_data[indx] is already NULL and has been kfreed. Don't pass that to sysfs_remove_group() as that
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: tracing: Free buffers when a used dynamic event is removed After 65536 dynamic events have been added and removed, the "type" field of the event then uses the first type number that is available (not currently
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: nvme: fix SRCU protection of nvme_ns_head list Walking the nvme_ns_head siblings list is protected by the head's srcu in nvme_ns_head_submit_bio() but not nvme_mpath_revalidate_paths(). Removing namespaces from
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: ipv4: Handle attempt to delete multipath route when fib_info contains an nh reference Gwangun Jung reported a slab-out-of-bounds access in fib_nh_match: fib_nh_match+0xf98/0x1130 linux-6.0-rc7/net/ipv4/fib_
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: mm/khugepaged: invoke MMU notifiers in shmem/file collapse paths Any codepath that zaps page table entries must invoke MMU notifiers to ensure that secondary MMUs (like KVM) don't keep accessing pages which are
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: memcg: fix possible use-after-free in memcg_write_event_control() memcg_write_event_control() accesses the dentry->d_name of the specified control fd to route the write call. As a cgroup interface file can't b
- affected < 5.3.18-150300.59.185.1fixed 5.3.18-150300.59.185.1
In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix race on per-CQ variable napi work_done After calling napi_complete_done(), the NAPIF_STATE_SCHED bit may be cleared, and another CPU can start napi thread and access per-CQ variable, cq->work_don
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: af_unix: Get user_ns from in_skb in unix_diag_get_exact(). Wei Chen reported a NULL deref in sk_user_ns() [0][1], and Paolo diagnosed the root cause: in unix_diag_get_exact(), the newly allocated skb does not h
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: NFC: nci: Bounds check struct nfc_target arrays While running under CONFIG_FORTIFY_SOURCE=y, syzkaller reported: memcpy: detected field-spanning write (size 129) of single field "target->sensf_res" at net/nf
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hisi_femac_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: net: hisilicon: Fix potential use-after-free in hix5hd2_rx() The skb is delivered to napi_gro_receive() which may free it, after calling this, dereferencing skb may trigger use-after-free.
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: ipv6: avoid use-after-free in ip6_fragment() Blamed commit claimed rcu_read_lock() was held by ip6_fragment() callers. It seems to not be always true, at least for UDP stack. syzbot reported: BUG: KASAN: use
- affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix u8 overflow By keep sending L2CAP_CONF_REQ packets, chan->num_conf_rsp increases multiple times and eventually it will wrap around the maximum number (i.e., 255). This patch prevents this
- CVE-2024-49995Oct 21, 2024affected < 5.3.18-150300.59.182.1fixed 5.3.18-150300.59.182.1
Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Page 33 of 76