VYPR

rpm package

suse/kernel-default&distro=SUSE Linux Enterprise Live Patching 15 SP5

pkg:rpm/suse/kernel-default&distro=SUSE%20Linux%20Enterprise%20Live%20Patching%2015%20SP5

Vulnerabilities (4,709)

  • CVE-2021-47425MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: i2c: acpi: fix resource leak in reconfiguration device addition acpi_i2c_find_adapter_by_handle() calls bus_find_device() which takes a reference on the adapter which is never released which will result in a re

  • CVE-2021-47424MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: i40e: Fix freeing of uninitialized misc IRQ vector When VSI set up failed in i40e_probe() as part of PF switch set up driver was trying to free misc IRQ vectors in i40e_clear_interrupt_scheme and produced a ker

  • CVE-2021-47423MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/debugfs: fix file release memory leak When using single_open() for opening, single_release() should be called, otherwise the 'op' allocated in single_open() will be leaked.

  • CVE-2021-47422MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: drm/nouveau/kms/nv50-: fix file release memory leak When using single_open() for opening, single_release() should be called, otherwise the 'op' allocated in single_open() will be leaked.

  • CVE-2021-47421MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: handle the case of pci_channel_io_frozen only in amdgpu_pci_resume In current code, when a PCI error state pci_channel_io_normal is detectd, it will report PCI_ERS_RESULT_CAN_RECOVER status to PCI d

  • CVE-2021-47420MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix a potential ttm->sg memory leak Memory is allocated for ttm->sg by kmalloc in kfd_mem_dmamap_userptr, but isn't freed by kfree in kfd_mem_dmaunmap_userptr. Free it!

  • CVE-2021-47419MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: net/sched: sch_taprio: properly cancel timer from taprio_destroy() There is a comment in qdisc_create() about us not calling ops->reset() in some cases. err_out4: /* * Any broken qdiscs that would require a

  • CVE-2021-47418MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: net_sched: fix NULL deref in fifo_set_limit() syzbot reported another NULL deref in fifo_set_limit() [1] I could repro the issue with : unshare -n tc qd add dev lo root handle 1:0 tbf limit 200000 burst 70000

  • CVE-2021-47417MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: libbpf: Fix memory leak in strset Free struct strset itself, not just its internal parts.

  • CVE-2021-47416MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: phy: mdio: fix memory leak Syzbot reported memory leak in MDIO bus interface, the problem was in wrong state logic. MDIOBUS_ALLOCATED indicates 2 states: 1. Bus is only allocated 2. Bus allocated and __mdiob

  • CVE-2021-47415MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: iwlwifi: mvm: Fix possible NULL dereference In __iwl_mvm_remove_time_event() check that 'te_data->vif' is NULL before dereferencing it.

  • CVE-2021-47414MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: riscv: Flush current cpu icache before other cpus On SiFive Unmatched, I recently fell onto the following BUG when booting: [ 0.000000] ftrace: allocating 36610 entries in 144 pages [ 0.000000] Oops - il

  • CVE-2021-47413MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: ci_hdrc_imx: Also search for 'phys' phandle When passing 'phys' in the devicetree to describe the USB PHY phandle (which is the recommended way according to Documentation/devicetree/bindings/usb/

  • CVE-2021-47412MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: block: don't call rq_qos_ops->done_bio if the bio isn't tracked rq_qos framework is only applied on request based driver, so: 1) rq_qos_done_bio() needn't to be called for bio based driver 2) rq_qos_done_bio(

  • CVE-2021-47410MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix svm_migrate_fini warning Device manager releases device-specific resources when a driver disconnects from a device, devm_memunmap_pages and devm_release_mem_region calls in svm_migrate_fini are

  • CVE-2021-47409MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: usb: dwc2: 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-2021-47408MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: conntrack: serialize hash resizes and cleanups Syzbot was able to trigger the following warning [1] No repro found by syzbot yet but I was able to trigger similar issue by having 2 scripts running i

  • CVE-2021-47407MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Handle SRCU initialization failure during page track init Check the return of init_srcu_struct(), which can fail due to OOM, when initializing the page track mechanism. Lack of checking leads to a NU

  • CVE-2021-47406MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: add error checking to ext4_ext_replay_set_iblocks() If the call to ext4_map_blocks() fails due to an corrupted file system, ext4_ext_replay_set_iblocks() can get stuck in an infinite loop. This could be

  • CVE-2021-47405MedMay 21, 2024
    affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

    In the Linux kernel, the following vulnerability has been resolved: HID: usbhid: free raw_report buffers in usbhid_stop Free the unsent raw_report buffers when the device is removed. Fixes a memory leak reported by syzbot at: https://syzkaller.appspot.com/bug?id=7b4fa7cb1a7c2d

Page 185 of 236