VYPR

rpm package

suse/kernel-default-base&distro=SUSE Linux Enterprise Micro 5.2

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20Micro%205.2

Vulnerabilities (1,696)

  • CVE-2024-56705Dec 28, 2024
    affected < 5.3.18-150300.59.207.1.150300.18.124.1fixed 5.3.18-150300.59.207.1.150300.18.124.1

    In the Linux kernel, the following vulnerability has been resolved: media: atomisp: Add check for rgby_data memory allocation failure In ia_css_3a_statistics_allocate(), there is no check on the allocation result of the rgby_data memory. If rgby_data is not successfully allocat

  • CVE-2024-56704Dec 28, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix release of IRQ Kernel logs indicate an IRQ was double-freed. Pass correct device ID during IRQ release. [Dominique: remove confusing variable reset to 0]

  • CVE-2024-56631HigDec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: sg: Fix slab-use-after-free read in sg_release() Fix a use-after-free bug in sg_release(), detected by syzbot with KASAN: BUG: KASAN: slab-use-after-free in lock_release+0x151/0xa30 kernel/locking/lockde

  • CVE-2024-56664Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Fix race between element replace and close() Element replace (with a socket different from the one stored) may race with socket's close() link popping & unlinking. __sock_map_delete() unconditiona

  • CVE-2024-56661Dec 27, 2024
    affected < 5.3.18-150300.59.204.1.150300.18.122.1fixed 5.3.18-150300.59.204.1.150300.18.122.1

    In the Linux kernel, the following vulnerability has been resolved: tipc: fix NULL deref in cleanup_bearer() syzbot found [1] that after blamed commit, ub->ubsock->sk was NULL when attempting the atomic_dec() : atomic_dec(&tipc_net(sock_net(ub->ubsock->sk))->wq_count); Fix th

  • CVE-2024-56658Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: net: defer final 'struct net' free in netns dismantle Ilya reported a slab-use-after-free in dst_destroy [1] Issue is in xfrm6_net_init() and xfrm4_net_init() : They copy xfrm[46]_dst_ops_template into net->x

  • CVE-2024-56651Dec 27, 2024
    affected < 5.3.18-150300.59.201.1.150300.18.120.1fixed 5.3.18-150300.59.201.1.150300.18.120.1

    In the Linux kernel, the following vulnerability has been resolved: can: hi311x: hi3110_can_ist(): fix potential use-after-free The commit a22bd630cfff ("can: hi311x: do not report txerr and rxerr during bus-off") removed the reporting of rxerr and txerr even in case of correct

  • CVE-2024-56650Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: x_tables: fix LED ID check in led_tg_check() Syzbot has reported the following BUG detected by KASAN: BUG: KASAN: slab-out-of-bounds in strlen+0x58/0x70 Read of size 1 at addr ffff8881022da0c8 by ta

  • CVE-2024-56642Dec 27, 2024
    affected < 5.3.18-150300.59.204.1.150300.18.122.1fixed 5.3.18-150300.59.204.1.150300.18.122.1

    In the Linux kernel, the following vulnerability has been resolved: tipc: Fix use-after-free of kernel socket in cleanup_bearer(). syzkaller reported a use-after-free of UDP kernel socket in cleanup_bearer() without repro. [0][1] When bearer_disable() calls tipc_udp_disable(),

  • CVE-2024-56623Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix use after free on unload System crash is observed with stack trace warning of use after free. There are 2 signals to tell dpc_thread to terminate (UNLOADING flag and kthread_stop). On settin

  • CVE-2024-56605Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create() bt_sock_alloc() allocates the sk object and attaches it to the provided sock object. On error l2cap_sock_alloc() frees the sk o

  • CVE-2024-56604Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but l

  • CVE-2024-56601Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: net: inet: do not leave a dangling sk pointer in inet_create() sock_init_data() attaches the allocated sk object to the provided sock object. If inet_create() fails later, the sk object is freed, but the sock o

  • CVE-2024-56600Dec 27, 2024
    affected < 5.3.18-150300.59.195.1.150300.18.116.1fixed 5.3.18-150300.59.195.1.150300.18.116.1

    In the Linux kernel, the following vulnerability has been resolved: net: inet6: do not leave a dangling sk pointer in inet6_create() sock_init_data() attaches the allocated sk pointer to the provided sock object. If inet6_create() fails later, the sk object is released, but the

  • CVE-2024-56558Dec 27, 2024
    affected < 5.3.18-150300.59.207.1.150300.18.124.1fixed 5.3.18-150300.59.207.1.150300.18.124.1

    In the Linux kernel, the following vulnerability has been resolved: nfsd: make sure exp active before svc_export_show The function `e_show` was called with protection from RCU. This only ensures that `exp` will not be freed. Therefore, the reference count for `exp` can drop to

  • CVE-2024-56548Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: hfsplus: don't query the device logical block size multiple times Devices block sizes may change. One of these cases is a loop device by using ioctl LOOP_SET_BLOCK_SIZE. While this may cause other issues like

  • CVE-2024-56539Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: mwifiex: Fix memcpy() field-spanning write warning in mwifiex_config_scan() Replace one-element array with a flexible-array member in `struct mwifiex_ie_types_wildcard_ssid_params` to fix the following wa

  • CVE-2024-53239Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: 6fire: Release resources at card release The current 6fire code tries to release the resources right after the call of usb6fire_chip_abort(). But at this moment, the card object might be still in use (as

  • CVE-2024-53214Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: vfio/pci: Properly hide first-in-list PCIe extended capability There are cases where a PCIe extended capability should be hidden from the user. For example, an unknown capability (i.e., capability with ID great

  • CVE-2024-53179Dec 27, 2024
    affected < 5.3.18-150300.59.188.1.150300.18.111.1fixed 5.3.18-150300.59.188.1.150300.18.111.1

    In the Linux kernel, the following vulnerability has been resolved: smb: client: fix use-after-free of signing key Customers have reported use-after-free in @ses->auth_key.response with SMB2.1 + sign mounts which occurs due to following race: task A tas

Page 35 of 85