VYPR

rpm package

suse/kernel-default-base&distro=SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS

pkg:rpm/suse/kernel-default-base&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP4-LTSS

Vulnerabilities (2,843)

  • CVE-2022-49349Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prepare We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 l

  • CVE-2022-49348Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: filter out EXT4_FC_REPLAY from on-disk superblock field s_state The EXT4_FC_REPLAY bit in sbi->s_mount_state is used to indicate that we are in the middle of replay the fast commit journal. This was actu

  • CVE-2022-49347Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in ext4_writepages we got issue as follows: EXT4-fs error (device loop0): ext4_mb_generate_buddy:1141: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free cls ------------[ c

  • CVE-2022-49346Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: net: dsa: lantiq_gswip: Fix refcount leak in gswip_gphy_fw_list Every iteration of for_each_available_child_of_node() decrements the reference count of the previous node. when breaking early from a for_each_ava

  • CVE-2022-49345Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: net: xfrm: unexport __init-annotated xfrm4_protocol_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols an

  • CVE-2022-49343Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid cycles in directory h-tree A maliciously corrupted filesystem can contain cycles in the h-tree stored inside a directory. That can easily lead to the kernel corrupting tree nodes that were already v

  • CVE-2022-49342Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: net: ethernet: bgmac: Fix refcount leak in bcma_mdio_mii_register of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of

  • CVE-2022-49341Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: bpf, arm64: Clear prog->jited_len along prog->jited syzbot reported an illegal copy_to_user() attempt from bpf_prog_get_info_by_fd() [1] There was no repro yet on this bug, but I think that commit 0aef499f3172

  • CVE-2022-49339Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: net: ipv6: unexport __init-annotated seg6_hmac_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotat

  • CVE-2022-49337Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock When user_dlm_destroy_lock failed, it didn't clean up the flags it set before exit. For USER_LOCK_IN_TEARDOWN, if this function fails because of lock i

  • CVE-2022-49336Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem When the mapping is already reaped the unmap must be a no-op, as we would otherwise try to remove the mapping twice, corrupting the involved data

  • CVE-2022-49335Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour. Submitting a cs with 0 chunks, causes an oops later, found trying to execute the wrong userspace driver. MESA_LOADER_DRIVER_OVERRIDE=v3d glxinfo [

  • CVE-2022-49332Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Address NULL pointer dereference after starget_to_rport() Calls to starget_to_rport() may return NULL. Add check for NULL rport before dereference.

  • CVE-2022-49331Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: nfc: st21nfca: fix memory leaks in EVT_TRANSACTION handling Error paths do not free previously allocated memory. Add devm_kfree() to those failure paths.

  • CVE-2022-49328Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: mt76: fix use-after-free by removing a non-RCU wcid pointer Fixes an issue caught by KASAN about use-after-free in mt76_txq_schedule by protecting mtxq->wcid with rcu_lock between mt76_txq_schedule and sta_info

  • CVE-2022-49327Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: bcache: avoid journal no-space deadlock by reserving 1 journal bucket The journal no-space deadlock was reported time to time. Such deadlock can happen in the following situation. When all journal buckets are

  • CVE-2022-49326Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@

  • CVE-2022-49323Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe() It will cause null-ptr-deref when using 'res', if platform_get_resource() returns NULL, so move using 'res' after devm_ioremap_resource() t

  • CVE-2022-49322Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: tracing: Fix sleeping function called from invalid context on RT kernel When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the cmdline, the output_printk() was called, and the spin_loc

  • CVE-2022-49321Feb 26, 2025
    affected < 5.14.21-150400.24.158.1.150400.24.78.1fixed 5.14.21-150400.24.158.1.150400.24.78.1

    In the Linux kernel, the following vulnerability has been resolved: xprtrdma: treat all calls not a bcall when bc_serv is NULL When a rdma server returns a fault format reply, nfs v3 client may treats it as a bcall when bc service is not exist. The debug message at rpcrdma_bc_

Page 78 of 143