p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-azure-5.15 · Page n° 192

Vulnérabilité publiée pour linux-azure-5.15 au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 4525

  1. CVE-2024-26846

    Moyenne · CVSS 4.4EPSS 0,22%Correctif disponible

    nvme-fc: do not wait in vain when unloading module

    In the Linux kernel, the following vulnerability has been resolved: nvme-fc: do not wait in vain when unloading module The module exit path has race between deleting all controllers and freeing 'left over IDs'. To prevent double free a synchronization between nvme_delete_ctrl and ida_destroy has been added by the initial commit. There is some logic around trying to prevent from hanging forever in wait_for_completion, though it does not handling all cases. E.g. blktests is able to reproduce the situation where the module unload hangs forever. If we completely rely on the cleanup code executed from the nvme_delete_ctrl path, all IDs will be

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  2. CVE-2024-26845

    Élevée · CVSS 7.5EPSS 0,74%Correctif disponible

    scsi: target: core: Add TMF to tmr_list handling

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: core: Add TMF to tmr_list handling An abort that is responded to by iSCSI itself is added to tmr_list but does not go to target core. A LUN_RESET that goes through tmr_list takes a refcounter on the abort and waits for completion. However, the abort will be never complete because it was not started in target core. Unable to locate ITT: 0x05000000 on CID: 0 Unable to locate RefTaskTag: 0x05000000 on CID: 0. wait_for_tasks: Stopping tmf LUN_RESET with tag 0x0 ref_task_tag 0x0 i_state 34 t_state ISTATE_PROCESSING refcnt 2 transport_state active,stop,fabric_st

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  3. CVE-2024-26843

    Moyenne · CVSS 6EPSS 0,23%Correctif disponible

    efi: runtime: Fix potential overflow of soft-reserved region size

    In the Linux kernel, the following vulnerability has been resolved: efi: runtime: Fix potential overflow of soft-reserved region size md_size will have been narrowed if we have >= 4GB worth of pages in a soft-reserved region.

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  4. CVE-2024-26840

    Moyenne · CVSS 5.5EPSS 0,28%Correctif disponible

    cachefiles: fix memory leak in cachefiles_add_cache()

    In the Linux kernel, the following vulnerability has been resolved: cachefiles: fix memory leak in cachefiles_add_cache() The following memory leak was reported after unbinding /dev/cachefiles: ================================================================== unreferenced object 0xffff9b674176e3c0 (size 192): comm "cachefilesd2", pid 680, jiffies 4294881224 hex dump (first 32 bytes): 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc ea38a44b): [<ffffffff8eb8a1a5>] kmem_cache_alloc+0x2d5/0x370 [<ffffffff8e917f86>] prepare_

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  5. CVE-2024-26839

    Moyenne · CVSS 5.5EPSS 0,24%Correctif disponible

    IB/hfi1: Fix a memleak in init_credit_return

    In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix a memleak in init_credit_return When dma_alloc_coherent fails to allocate dd->cr_base[i].va, init_credit_return should deallocate dd->cr_base and dd->cr_base[i] that allocated before. Or those resources would be never freed and a memleak is triggered.

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  6. CVE-2024-26838

    Élevée · CVSS 7.8EPSS 0,24%Correctif disponible

    RDMA/irdma: Fix KASAN issue with tasklet

    In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Fix KASAN issue with tasklet KASAN testing revealed the following issue assocated with freeing an IRQ. [50006.466686] Call Trace: [50006.466691] <IRQ> [50006.489538] dump_stack+0x5c/0x80 [50006.493475] print_address_description.constprop.6+0x1a/0x150 [50006.499872] ? irdma_sc_process_ceq+0x483/0x790 [irdma] [50006.505742] ? irdma_sc_process_ceq+0x483/0x790 [irdma] [50006.511644] kasan_report.cold.11+0x7f/0x118 [50006.516572] ? irdma_sc_process_ceq+0x483/0x790 [irdma] [50006.522473] irdma_sc_process_ceq+0x483/0x790 [irdma] [50006.528232] irdma_process_c

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  7. CVE-2024-26837

    Moyenne · CVSS 4.7EPSS 0,17%Correctif disponible

    net: bridge: switchdev: Skip MDB replays of deferred events on offload

    In the Linux kernel, the following vulnerability has been resolved: net: bridge: switchdev: Skip MDB replays of deferred events on offload Before this change, generation of the list of MDB events to replay would race against the creation of new group memberships, either from the IGMP/MLD snooping logic or from user configuration. While new memberships are immediately visible to walkers of br->mdb_list, the notification of their existence to switchdev event subscribers is deferred until a later point in time. So if a replay list was generated during a time that overlapped with such a window, it would also contain a replay of the not-yet-del

    • Mettez à jour vers 5.15.0-1087.96~20.04.1
    Publication Mise à jour
  8. CVE-2024-26835

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    netfilter: nf_tables: set dormant flag on hook register failure

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: set dormant flag on hook register failure We need to set the dormant flag again if we fail to register the hooks. During memory pressure hook registration can fail and we end up with a table marked as active but no registered hooks. On table/base chain deletion, nf_tables will attempt to unregister the hook again which yields a warn splat from the nftables core.

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  9. CVE-2024-26833

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    drm/amd/display: Fix memory leak in dm_sw_fini()

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix memory leak in dm_sw_fini() After destroying dmub_srv, the memory associated with it is not freed, causing a memory leak: unreferenced object 0xffff896302b45800 (size 1024): comm "(udev-worker)", pid 222, jiffies 4294894636 hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ backtrace (crc 6265fd77): [<ffffffff993495ed>] kmalloc_trace+0x29d/0x340 [<ffffffffc0ea4a94>] dm_dmub_sw_init+0xb4/0x450 [amdgpu] [<ffffffffc0ea4e55>

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour
  10. CVE-2024-26829

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    media: ir_toy: fix a memleak in irtoy_tx

    In the Linux kernel, the following vulnerability has been resolved: media: ir_toy: fix a memleak in irtoy_tx When irtoy_command fails, buf should be freed since it is allocated by irtoy_tx, or there is a memleak.

    • Mettez à jour vers 5.15.0-1063.72~20.04.1
    Publication Mise à jour
  11. CVE-2024-26830

    Élevée · CVSS 8.4EPSS 0,23%Correctif disponible

    i40e: Do not allow untrusted VF to remove administratively set MAC

    In the Linux kernel, the following vulnerability has been resolved: i40e: Do not allow untrusted VF to remove administratively set MAC Currently when PF administratively sets VF's MAC address and the VF is put down (VF tries to delete all MACs) then the MAC is removed from MAC filters and primary VF MAC is zeroed. Do not allow untrusted VF to remove primary MAC when it was set administratively by PF. Reproducer: 1) Create VF 2) Set VF interface up 3) Administratively set the VF's MAC 4) Put VF interface down [root@host ~]# echo 1 > /sys/class/net/enp2s0f0/device/sriov_numvfs [root@host ~]# ip link set enp2s0f0v0 up [root@host ~]# ip link

    • Mettez à jour vers 5.15.0-1071.80~20.04.1
    Publication Mise à jour
  12. CVE-2024-26828

    Critique · CVSS 9.4EPSS 0,75%Correctif disponible

    cifs: fix underflow in parse_server_interfaces()

    In the Linux kernel, the following vulnerability has been resolved: cifs: fix underflow in parse_server_interfaces() In this loop, we step through the buffer and after each item we check if the size_left is greater than the minimum size we need. However, the problem is that "bytes_left" is type ssize_t while sizeof() is type size_t. That means that because of type promotion, the comparison is done as an unsigned and if we have negative bytes left the loop continues instead of ending.

    • Mettez à jour vers 5.15.0-1068.77~20.04.1
    Publication Mise à jour
  13. CVE-2024-26826

    Élevée · CVSS 7.5EPSS 0,65%Correctif disponible

    mptcp: fix data re-injection from stale subflow

    In the Linux kernel, the following vulnerability has been resolved: mptcp: fix data re-injection from stale subflow When the MPTCP PM detects that a subflow is stale, all the packet scheduler must re-inject all the mptcp-level unacked data. To avoid acquiring unneeded locks, it first try to check if any unacked data is present at all in the RTX queue, but such check is currently broken, as it uses TCP-specific helper on an MPTCP socket. Funnily enough fuzzers and static checkers are happy, as the accessed memory still belongs to the mptcp_sock struct, and even from a functional perspective the recovery completed successfully, as the short-

    • Mettez à jour vers 5.15.0-1063.72~20.04.1
    Publication Mise à jour
  14. CVE-2024-26825

    Moyenne · CVSS 5.5EPSS 0,24%Correctif disponible

    nfc: nci: free rx_data_reassembly skb on NCI device cleanup

    In the Linux kernel, the following vulnerability has been resolved: nfc: nci: free rx_data_reassembly skb on NCI device cleanup rx_data_reassembly skb is stored during NCI data exchange for processing fragmented packets. It is dropped only when the last fragment is processed or when an NTF packet with NCI_OP_RF_DEACTIVATE_NTF opcode is received. However, the NCI device may be deallocated before that which leads to skb leak. As by design the rx_data_reassembly skb is bound to the NCI device and nothing prevents the device to be freed before the skb is processed in some way and cleaned, free it on the NCI device cleanup. Found by Linux Veri

    • Mettez à jour vers 5.15.0-1063.72~20.04.1
    Publication Mise à jour
  15. CVE-2024-26822

    Élevée · CVSS 8.7EPSS 0,23%Correctif disponible

    smb: client: set correct id, uid and cruid for multiuser automounts

    In the Linux kernel, the following vulnerability has been resolved: smb: client: set correct id, uid and cruid for multiuser automounts When uid, gid and cruid are not specified, we need to dynamically set them into the filesystem context used for automounting otherwise they'll end up reusing the values from the parent mount.

    • Mettez à jour vers 5.15.0-1078.87~20.04.1
    Publication Mise à jour
  16. CVE-2023-52643

    Moyenne · CVSS 5.5EPSS 0,22%Correctif disponible

    iio: core: fix memleak in iio_device_register_sysfs

    In the Linux kernel, the following vulnerability has been resolved: iio: core: fix memleak in iio_device_register_sysfs When iio_device_register_sysfs_group() fails, we should free iio_dev_opaque->chan_attr_group.attrs to prevent potential memleak.

    • Mettez à jour vers 5.15.0-1063.72~20.04.1
    Publication Mise à jour
  17. CVE-2024-24856

    Moyenne · CVSS 5.3EPSS 0,17%Correctif disponible

    NULL pointer deference in acpi_db_convert_to_package of Linux acpi module

    The memory allocation function ACPI_ALLOCATE_ZEROED does not guarantee a successful allocation, but the subsequent code directly dereferences the pointer that receives it, which may lead to null pointer dereference. To fix this issue, a null pointer check should be added. If it is null, return exception code AE_NO_MEMORY.

    • Mettez à jour vers 5.15.0-1046.53~20.04.1
    Publication Mise à jour
  18. CVE-2024-26817

    Moyenne · CVSS 5.5EPSS 0,76%Correctif disponible

    amdkfd: use calloc instead of kzalloc to avoid integer overflow

    In the Linux kernel, the following vulnerability has been resolved: amdkfd: use calloc instead of kzalloc to avoid integer overflow This uses calloc instead of doing the multiplication which might overflow.

    • Mettez à jour vers 5.15.0-1068.77~20.04.1
    Publication Mise à jour
  19. CVE-2024-26816

    Moyenne · CVSS 5.5EPSS 0,31%Correctif disponible

    x86, relocs: Ignore relocations in .notes section

    In the Linux kernel, the following vulnerability has been resolved: x86, relocs: Ignore relocations in .notes section When building with CONFIG_XEN_PV=y, .text symbols are emitted into the .notes section so that Xen can find the "startup_xen" entry point. This information is used prior to booting the kernel, so relocations are not useful. In fact, performing relocations against the .notes section means that the KASLR base is exposed since /sys/kernel/notes is world-readable. To avoid leaking the KASLR base without breaking unprivileged tools that are expecting to read /sys/kernel/notes, skip performing relocations in the .notes section. Th

    • Mettez à jour vers 5.15.0-1065.74~20.04.1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →