VYPR

rpm package

suse/kernel-source&distro=SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS

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

Vulnerabilities (2,318)

  • CVE-2022-49335MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49333MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: E-Switch, pair only capable devices OFFLOADS paring using devcom is possible only on devices that support LAG. Filter based on lag capabilities. This fixes an issue where mlx5_get_next_phys_dev() was

  • CVE-2022-49332MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49331MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49330MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: tcp: fix tcp_mtup_probe_success vs wrong snd_cwnd syzbot got a new report [1] finally pointing to a very old bug, added in initial support for MTU probing. tcp_mtu_probe() has checks about starting an MTU prob

  • CVE-2022-49329MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: vduse: Fix NULL pointer dereference on sysfs access The control device has no drvdata. So we will get a NULL pointer dereference when accessing control device's msg_timeout attribute via sysfs: [ 132.841881][

  • CVE-2022-49328HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49327MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49326MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49325MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: tcp: add accessors to read/set tp->snd_cwnd We had various bugs over the years with code breaking the assumption that tp->snd_cwnd is greater than zero. Lately, syzbot reported the WARN_ON_ONCE(!tp->prior_cwnd

  • CVE-2022-49323MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49322MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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-49321MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.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_

  • CVE-2022-49320MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type In zynqmp_dma_alloc/free_chan_resources functions there is a potential overflow in the below expressions. dma_alloc_coherent(chan->dev,

  • CVE-2022-49319MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: iommu/arm-smmu-v3: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value.

  • CVE-2022-49316MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: NFSv4: Don't hold the layoutget locks across multiple RPC calls When doing layoutget as part of the open() compound, we have to be careful to release the layout locks before we can call any further RPC calls, s

  • CVE-2022-49315MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: drivers: staging: rtl8192e: Fix deadlock in rtllib_beacons_stop() There is a deadlock in rtllib_beacons_stop(), which is shown below: (Thread 1) | (Thread 2) | r

  • CVE-2022-49314MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: tty: Fix a possible resource leak in icom_probe When pci_read_config_dword failed, call pci_release_regions() and pci_disable_device() to recycle the resource previously allocated.

  • CVE-2022-49313MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: drivers: usb: host: Fix deadlock in oxu_bus_suspend() There is a deadlock in oxu_bus_suspend(), which is shown below: (Thread 1) | (Thread 2) | timer_action() ox

  • CVE-2022-49312MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: staging: rtl8712: fix a potential memory leak in r871xu_drv_init() In r871xu_drv_init(), if r8712_init_drv_sw() fails, then the memory allocated by r8712_alloc_io_queue() in r8712_usb_dvobj_init() is not proper

Page 91 of 116