p PatchFirst

PatchFirst · Latest vulnerabilities

linux-azure-5.15 vulnerabilities · Page 108

Vulnerabilities published for linux-azure-5.15 in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 4525

  1. CVE-2022-49147

    Medium · CVSS 5.5EPSS 0.26%Fix available

    block: Fix the maximum minor value is blk_alloc_ext_minor()

    In the Linux kernel, the following vulnerability has been resolved: block: Fix the maximum minor value is blk_alloc_ext_minor() ida_alloc_range(..., min, max, ...) returns values from min to max, inclusive. So, NR_EXT_DEVT is a valid idx returned by blk_alloc_ext_minor(). This is an issue because in device_add_disk(), this value is used in: ddev->devt = MKDEV(disk->major, disk->first_minor); and NR_EXT_DEVT is '(1 << MINORBITS)'. So, should 'disk->first_minor' be NR_EXT_DEVT, it would overflow.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  2. CVE-2022-49145

    High · CVSS 7.1EPSS 0.28%Fix available

    ACPI: CPPC: Avoid out of bounds access when parsing _CPC data

    In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Avoid out of bounds access when parsing _CPC data If the NumEntries field in the _CPC return package is less than 2, do not attempt to access the "Revision" element of that package, because it may not be present then. BugLink: https://lore.kernel.org/lkml/20220322143534.GC32582@xsang-OptiPlex-9020/

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  3. CVE-2022-49144

    Medium · CVSS 5.5EPSS 0.26%Fix available

    io_uring: fix memory leak of uid in files registration

    In the Linux kernel, the following vulnerability has been resolved: io_uring: fix memory leak of uid in files registration When there are no files for __io_sqe_files_scm() to process in the range, it'll free everything and return. However, it forgets to put uid.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  4. CVE-2022-49142

    High · CVSS 7.5EPSS 0.64%Fix available

    net: preserve skb_end_offset() in skb_unclone_keeptruesize()

    In the Linux kernel, the following vulnerability has been resolved: net: preserve skb_end_offset() in skb_unclone_keeptruesize() syzbot found another way to trigger the infamous WARN_ON_ONCE(delta < len) in skb_try_coalesce() [1] I was able to root cause the issue to kfence. When kfence is in action, the following assertion is no longer true: int size = xxxx; void *ptr1 = kmalloc(size, gfp); void *ptr2 = kmalloc(size, gfp); if (ptr1 && ptr2) ASSERT(ksize(ptr1) == ksize(ptr2)); We attempted to fix these issues in the blamed commits, but forgot that TCP was possibly shifting data after skb_unclone_keeptruesize() has been used, notably f

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  5. CVE-2022-49139

    Medium · CVSS 5.5EPSS 0.27%Fix available

    Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: fix null ptr deref on hci_sync_conn_complete_evt This event is just specified for SCO and eSCO link types. On the reception of a HCI_Synchronous_Connection_Complete for a BDADDR of an existing LE connection, LE link type and a status that triggers the second case of the packet processing a NULL pointer dereference happens, as conn->link is NULL.

    • Update to 5.15.0-1036.43~20.04.1
    Published Updated
  6. CVE-2022-49137

    Medium · CVSS 5.5EPSS 0.27%Fix available

    drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/amdgpu/amdgpu_cs: fix refcount leak of a dma_fence obj This issue takes place in an error path in amdgpu_cs_fence_to_handle_ioctl(). When `info->in.what` falls into default case, the function simply returns -EINVAL, forgetting to decrement the reference count of a dma_fence obj, which is bumped earlier by amdgpu_cs_get_fence(). This may result in reference count leaks. Fix it by decreasing the refcount of specific object before returning the error code.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  7. CVE-2022-49135

    Medium · CVSS 5.5EPSS 0.27%Fix available

    drm/amd/display: Fix memory leak

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak [why] Resource release is needed on the error handling path to prevent memory leak. [how] Fix this by adding kfree on the error handling path.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  8. CVE-2022-49132

    Medium · CVSS 5.5EPSS 0.26%Fix available

    ath11k: pci: fix crash on suspend if board file is not found

    In the Linux kernel, the following vulnerability has been resolved: ath11k: pci: fix crash on suspend if board file is not found Mario reported that the kernel was crashing on suspend if ath11k was not able to find a board file: [ 473.693286] PM: Suspending system (s2idle) [ 473.693291] printk: Suspending console(s) (use no_console_suspend to debug) [ 474.407787] BUG: unable to handle page fault for address: 0000000000002070 [ 474.407791] #PF: supervisor read access in kernel mode [ 474.407794] #PF: error_code(0x0000) - not-present page [ 474.407798] PGD 0 P4D 0 [ 474.407801] Oops: 0000 [#1] PREEMPT SMP NOPTI [ 474.407805] CPU: 2 P

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  9. CVE-2022-49131

    Medium · CVSS 5.5EPSS 0.26%Fix available

    ath11k: fix kernel panic during unload/load ath11k modules

    In the Linux kernel, the following vulnerability has been resolved: ath11k: fix kernel panic during unload/load ath11k modules Call netif_napi_del() from ath11k_ahb_free_ext_irq() to fix the following kernel panic when unload/load ath11k modules for few iterations. [ 971.201365] Unable to handle kernel paging request at virtual address 6d97a208 [ 971.204227] pgd = 594c2919 [ 971.211478] [6d97a208] *pgd=00000000 [ 971.214120] Internal error: Oops: 5 [#1] PREEMPT SMP ARM [ 971.412024] CPU: 2 PID: 4435 Comm: insmod Not tainted 5.4.89 #0 [ 971.434256] Hardware name: Generic DT based system [ 971.440165] PC is at napi_by_id+0x10/0x40 [

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  10. CVE-2022-49130

    Medium · CVSS 5.5EPSS 0.26%Fix available

    ath11k: mhi: use mhi_sync_power_up()

    In the Linux kernel, the following vulnerability has been resolved: ath11k: mhi: use mhi_sync_power_up() If amss.bin was missing ath11k would crash during 'rmmod ath11k_pci'. The reason for that was that we were using mhi_async_power_up() which does not check any errors. But mhi_sync_power_up() on the other hand does check for errors so let's use that to fix the crash. I was not able to find a reason why an async version was used. ath11k_mhi_start() (which enables state ATH11K_MHI_POWER_ON) is called from ath11k_hif_power_up(), which can sleep. So sync version should be safe to use here. [ 145.569731] general protection fault, probably f

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  11. CVE-2022-49129

    High · CVSS 7.8EPSS 0.27%Fix available

    mt76: mt7921: fix crash when startup fails.

    In the Linux kernel, the following vulnerability has been resolved: mt76: mt7921: fix crash when startup fails. If the nic fails to start, it is possible that the reset_work has already been scheduled. Ensure the work item is canceled so we do not have use-after-free crash in case cleanup is called before the work item is executed. This fixes crash on my x86_64 apu2 when mt7921k radio fails to work. Radio still fails, but OS does not crash.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  12. CVE-2022-49128

    Medium · CVSS 5.5EPSS 0.26%Fix available

    drm/bridge: Add missing pm_runtime_put_sync

    In the Linux kernel, the following vulnerability has been resolved: drm/bridge: Add missing pm_runtime_put_sync pm_runtime_get_sync() will increase the rumtime PM counter even when it returns an error. Thus a pairing decrement is needed to prevent refcount leak. Fix this by replacing this API with pm_runtime_resume_and_get(), which will not change the runtime PM counter on error. Besides, a matching decrement is needed on the error handling path to keep the counter balanced.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  13. CVE-2022-49122

    Medium · CVSS 5.5EPSS 0.31%Fix available

    dm ioctl: prevent potential spectre v1 gadget

    In the Linux kernel, the following vulnerability has been resolved: dm ioctl: prevent potential spectre v1 gadget It appears like cmd could be a Spectre v1 gadget as it's supplied by a user and used as an array index. Prevent the contents of kernel memory from being leaked to userspace via speculative execution by using array_index_nospec.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  14. CVE-2022-49121

    Medium · CVSS 5.5EPSS 0.27%Fix available

    scsi: pm8001: Fix tag leaks on error

    In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix tag leaks on error In pm8001_chip_set_dev_state_req(), pm8001_chip_fw_flash_update_req(), pm80xx_chip_phy_ctl_req() and pm8001_chip_reg_dev_req() add missing calls to pm8001_tag_free() to free the allocated tag when pm8001_mpi_build_cmd() fails. Similarly, in pm8001_exec_internal_task_abort(), if the chip ->task_abort method fails, the tag allocated for the abort request task must be freed. Add the missing call to pm8001_tag_free().

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  15. CVE-2022-49120

    Medium · CVSS 5.5EPSS 0.27%Fix available

    scsi: pm8001: Fix task leak in pm8001_send_abort_all()

    In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix task leak in pm8001_send_abort_all() In pm8001_send_abort_all(), make sure to free the allocated sas task if pm8001_tag_alloc() or pm8001_mpi_build_cmd() fail.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  16. CVE-2022-49119

    Medium · CVSS 5.5EPSS 0.27%Fix available

    scsi: pm8001: Fix memory leak in pm8001_chip_fw_flash_update_req()

    In the Linux kernel, the following vulnerability has been resolved: scsi: pm8001: Fix memory leak in pm8001_chip_fw_flash_update_req() In pm8001_chip_fw_flash_update_build(), if pm8001_chip_fw_flash_update_build() fails, the struct fw_control_ex allocated must be freed.

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated
  17. CVE-2022-49118

    Medium · CVSS 5.5EPSS 0.27%Fix available

    scsi: hisi_sas: Free irq vectors in order for v3 HW

    In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Free irq vectors in order for v3 HW If the driver probe fails to request the channel IRQ or fatal IRQ, the driver will free the IRQ vectors before freeing the IRQs in free_irq(), and this will cause a kernel BUG like this: ------------[ cut here ]------------ kernel BUG at drivers/pci/msi.c:369! Internal error: Oops - BUG: 0 [#1] PREEMPT SMP Call trace: free_msi_irqs+0x118/0x13c pci_disable_msi+0xfc/0x120 pci_free_irq_vectors+0x24/0x3c hisi_sas_v3_probe+0x360/0x9d0 [hisi_sas_v3_hw] local_pci_probe+0x44/0xb0 work_for_cpu_fn+0x20/0x34 pro

    • Update to 5.15.0-1008.9~20.04.1
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →