VYPR

rpm package

suse/kernel-64kb&distro=SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS

pkg:rpm/suse/kernel-64kb&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP3-LTSS

Vulnerabilities (1,350)

  • CVE-2022-49082HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: mpt3sas: Fix use after free in _scsih_expander_node_remove() The function mpt3sas_transport_port_remove() called in _scsih_expander_node_remove() frees the port field of the sas_expander structure, leadin

  • CVE-2022-49080MedFeb 26, 2025
    affected < 5.3.18-150300.59.198.1fixed 5.3.18-150300.59.198.1

    In the Linux kernel, the following vulnerability has been resolved: mm/mempolicy: fix mpol_new leak in shared_policy_replace If mpol_new is allocated but not used in restart loop, mpol_new will be freed via mpol_put before returning to the caller. But refcnt is not initialized

  • CVE-2022-49078HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: lz4: fix LZ4_decompress_safe_partial read out of bound When partialDecoding, it is EOF if we've either filled the output buffer or can't proceed with reading an offset for following match. In some extreme corn

  • CVE-2022-49076HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: RDMA/hfi1: Fix use-after-free bug for mm struct Under certain conditions, such as MPI_Abort, the hfi1 cleanup code may represent the last reference held on the task mm. hfi1_mmu_rb_unregister() then drops the l

  • CVE-2022-49073HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: ata: sata_dwc_460ex: Fix crash due to OOB write the driver uses libata's "tag" values from in various arrays. Since the mentioned patch bumped the ATA_TAG_INTERNAL to 32, the value of the SATA_DWC_QCMD_MAX need

  • CVE-2022-49065MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix the svc_deferred_event trace class Fix a NULL deref crash that occurs when an svc_rqst is deferred while the sunrpc tracing subsystem is enabled. svc_revisit() sets dr->xprt to NULL, so it can't be

  • CVE-2022-49063HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: ice: arfs: fix use-after-free when freeing @rx_cpu_rmap The CI testing bots triggered the following splat: [ 718.203054] BUG: KASAN: use-after-free in free_irq_cpu_rmap+0x53/0x80 [ 718.206349] Read of size 4

  • CVE-2022-49059HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: nfc: nci: add flush_workqueue to prevent uaf Our detector found a concurrent use-after-free bug when detaching an NCI device. The main reason for this bug is the unexpected scheduling between the used delayed m

  • CVE-2022-49058HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: cifs: potential buffer overflow in handling symlinks Smatch printed a warning: arch/x86/crypto/poly1305_glue.c:198 poly1305_update_arch() error: __memcpy() 'dctx->buf' too small (16 vs u32max) It's caused be

  • CVE-2022-49055MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check for potential null return of kmalloc_array() As the kmalloc_array() may return null, the 'event_waiters[i].wait' would lead to null-pointer dereference. Therefore, it is better to check the re

  • CVE-2022-49053HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: tcmu: Fix possible page UAF tcmu_try_get_data_page() looks up pages under cmdr_lock, but it does not take refcount properly and just returns page pointer. When tcmu_try_get_data_page() returns, th

  • CVE-2022-49051MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: net: usb: aqc111: Fix out-of-bounds accesses in RX fixup aqc111_rx_fixup() contains several out-of-bounds accesses that can be triggered by a malicious (or defective) USB device, in particular: - The metadata

  • CVE-2022-49044HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: dm integrity: fix memory corruption when tag_size is less than digest size It is possible to set up dm-integrity in such a way that the "tag_size" parameter is less than the actual digest size. In this situatio

  • CVE-2021-47659MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: drm/plane: Move range check for format_count earlier While the check for format_count > 64 in __drm_universal_plane_init() shouldn't be hit (it's a WARN_ON), in its current position it will then leak the plane-

  • CVE-2021-47653HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: media: davinci: vpif: fix use-after-free on driver unbind The driver allocates and registers two platform device structures during probe, but the devices were never deregistered on driver unbind. This results

  • CVE-2021-47652MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: video: fbdev: smscufx: Fix null-ptr-deref in ufx_usb_probe() I got a null-ptr-deref report: BUG: kernel NULL pointer dereference, address: 0000000000000000 ... RIP: 0010:fb_destroy_modelist+0x38/0x100 ... Call

  • CVE-2021-47651MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: soc: qcom: rpmpd: Check for null return of devm_kcalloc Because of the possible failure of the allocation, data->domains might be NULL pointer and will cause the dereference of the NULL pointer later. Therefore

  • CVE-2021-47650MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: soc-compress: prevent the potentially use of null pointer There is one call trace that snd_soc_register_card() ->snd_soc_bind_card()->soc_init_pcm_runtime() ->snd_soc_dai_compress_new()->snd_soc_new_compr

  • CVE-2021-47642HigFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: video: fbdev: nvidiafb: Use strscpy() to prevent buffer overflow Coverity complains of a possible buffer overflow. However, given the 'static' scope of nvidia_setup_i2c_bus() it looks like that can't happen aft

  • CVE-2021-47641MedFeb 26, 2025
    affected < 5.3.18-150300.59.201.1fixed 5.3.18-150300.59.201.1

    In the Linux kernel, the following vulnerability has been resolved: video: fbdev: cirrusfb: check pixclock to avoid divide by zero Do a sanity check on pixclock value to avoid divide by zero. If the pixclock value is zero, the cirrusfb driver will round up pixclock to get the

Page 22 of 68