p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-intel-iotg-5.15 · Seite 118

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-intel-iotg-5.15: 0. Davon im KEV-Katalog: 0.

RSS ↗ JSON ↗
Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4693

  1. CVE-2024-56756

    Mittel · CVSS 5.5EPSS 0,22%Korrektur verfügbar

    nvme-pci: fix freeing of the HMB descriptor table

    In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix freeing of the HMB descriptor table The HMB descriptor table is sized to the maximum number of descriptors that could be used for a given device, but __nvme_alloc_host_mem could break out of the loop earlier on memory allocation failure and end up using less descriptors than planned for, which leads to an incorrect size passed to dma_free_coherent. In practice this was not showing up because the number of descriptors tends to be low and the dma coherent allocator always allocates and frees at least a page.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  2. CVE-2024-56754

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    crypto: caam - Fix the pointer passed to caam_qi_shutdown()

    In the Linux kernel, the following vulnerability has been resolved: crypto: caam - Fix the pointer passed to caam_qi_shutdown() The type of the last parameter given to devm_add_action_or_reset() is "struct caam_drv_private *", but in caam_qi_shutdown(), it is casted to "struct device *". Pass the correct parameter to devm_add_action_or_reset() so that the resources are released as expected.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  3. CVE-2024-56748

    Niedrig · CVSS 3.3EPSS 0,23%Korrektur verfügbar

    scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb()

    In the Linux kernel, the following vulnerability has been resolved: scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb() Hook "qed_ops->common->sb_init = qed_sb_init" does not release the DMA memory sb_virt when it fails. Add dma_free_coherent() to free it. This is the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  4. CVE-2024-56747

    Niedrig · CVSS 3.3EPSS 0,23%Korrektur verfügbar

    scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()

    In the Linux kernel, the following vulnerability has been resolved: scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb() Hook "qedi_ops->common->sb_init = qed_sb_init" does not release the DMA memory sb_virt when it fails. Add dma_free_coherent() to free it. This is the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  5. CVE-2024-56746

    Niedrig · CVSS 3.3EPSS 0,22%Korrektur verfügbar

    fbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()

    In the Linux kernel, the following vulnerability has been resolved: fbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem() When information such as info->screen_base is not ready, calling sh7760fb_free_mem() does not release memory correctly. Call dma_free_coherent() instead.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  6. CVE-2024-56745

    Niedrig · CVSS 3.3EPSS 0,21%Korrektur verfügbar

    PCI: Fix reset_method_store() memory leak

    In the Linux kernel, the following vulnerability has been resolved: PCI: Fix reset_method_store() memory leak In reset_method_store(), a string is allocated via kstrndup() and assigned to the local "options". options is then used in with strsep() to find spaces: while ((name = strsep(&options, " ")) != NULL) { If there are no remaining spaces, then options is set to NULL by strsep(), so the subsequent kfree(options) doesn't free the memory allocated via kstrndup(). Fix by using a separate tmp_options to iterate with strsep() so options is preserved.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  7. CVE-2024-56739

    Mittel · CVSS 5.5EPSS 0,23%Korrektur verfügbar

    rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

    In the Linux kernel, the following vulnerability has been resolved: rtc: check if __rtc_read_time was successful in rtc_timer_do_work() If the __rtc_read_time call fails,, the struct rtc_time tm; may contain uninitialized data, or an illegal date/time read from the RTC hardware. When calling rtc_tm_to_ktime later, the result may be a very large value (possibly KTIME_MAX). If there are periodic timers in rtc->timerqueue, they will continually expire, may causing kernel softlockup.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  8. CVE-2024-56728

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c

    In the Linux kernel, the following vulnerability has been resolved: octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c Add error pointer check after calling otx2_mbox_get_rsp().

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  10. CVE-2024-56724

    Mittel · CVSS 5.5EPSS 0,22%Korrektur verfügbar

    mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device

    In the Linux kernel, the following vulnerability has been resolved: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ). Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  11. CVE-2024-56723

    Mittel · CVSS 5.5EPSS 0,23%Korrektur verfügbar

    mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices

    In the Linux kernel, the following vulnerability has been resolved: mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices While design wise the idea of converting the driver to use the hierarchy of the IRQ chips is correct, the implementation has (inherited) flaws. This was unveiled when platform_get_irq() had started WARN() on IRQ 0 that is supposed to be a Linux IRQ number (also known as vIRQ). Rework the driver to respect IRQ domain when creating each MFD device separately, as the domain is not the same for all of them.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  12. CVE-2024-56721

    Hoch · CVSS 7.1EPSS 0,23%Korrektur verfügbar

    x86/CPU/AMD: Terminate the erratum_1386_microcode array

    In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Terminate the erratum_1386_microcode array The erratum_1386_microcode array requires an empty entry at the end. Otherwise x86_match_cpu_with_stepping() will continue iterate the array after it ended. Add an empty entry to erratum_1386_microcode to its end.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1079.85~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  13. CVE-2024-56720

    Hoch · CVSS 7.8EPSS 0,24%Korrektur verfügbar

    bpf, sockmap: Several fixes to bpf_msg_pop_data

    In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Several fixes to bpf_msg_pop_data Several fixes to bpf_msg_pop_data, 1. In sk_msg_shift_left, we should put_page 2. if (len == 0), return early is better 3. pop the entire sk_msg (last == msg->sg.size) should be supported 4. Fix for the value of variable "a" 5. In sk_msg_shift_left, after shifting, i has already pointed to the next element. Addtional sk_msg_iter_var_next may result in BUG.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  14. CVE-2024-56716

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    netdevsim: prevent bad user input in nsim_dev_health_break_write()

    In the Linux kernel, the following vulnerability has been resolved: netdevsim: prevent bad user input in nsim_dev_health_break_write() If either a zero count or a large one is provided, kernel can crash.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  15. CVE-2024-56715

    Hoch · CVSS 7.8EPSS 0,26%Korrektur verfügbar

    ionic: Fix netdev notifier unregister on failure

    In the Linux kernel, the following vulnerability has been resolved: ionic: Fix netdev notifier unregister on failure If register_netdev() fails, then the driver leaks the netdev notifier. Fix this by calling ionic_lif_unregister() on register_netdev() failure. This will also call ionic_lif_unregister_phc() if it has already been registered.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  16. CVE-2024-56708

    Hoch · CVSS 7.8EPSS 0,25%Korrektur verfügbar

    EDAC/igen6: Avoid segmentation fault on module unload

    In the Linux kernel, the following vulnerability has been resolved: EDAC/igen6: Avoid segmentation fault on module unload The segmentation fault happens because: During modprobe: 1. In igen6_probe(), igen6_pvt will be allocated with kzalloc() 2. In igen6_register_mci(), mci->pvt_info will point to &igen6_pvt->imc[mc] During rmmod: 1. In mci_release() in edac_mc.c, it will kfree(mci->pvt_info) 2. In igen6_remove(), it will kfree(igen6_pvt); Fix this issue by setting mci->pvt_info to NULL to avoid the double kfree.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  17. CVE-2024-56705

    Mittel · CVSS 5.7EPSS 0,27%Korrektur verfügbar

    media: atomisp: Add check for rgby_data memory allocation failure

    In the Linux kernel, the following vulnerability has been resolved: media: atomisp: Add check for rgby_data memory allocation failure In ia_css_3a_statistics_allocate(), there is no check on the allocation result of the rgby_data memory. If rgby_data is not successfully allocated, it may trigger the assert(host_stats->rgby_data) assertion in ia_css_s3a_hmem_decode(). Adding a check to fix this potential issue.

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  18. CVE-2024-56704

    Hoch · CVSS 8.4EPSS 0,24%Korrektur verfügbar

    9p/xen: fix release of IRQ

    In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix release of IRQ Kernel logs indicate an IRQ was double-freed. Pass correct device ID during IRQ release. [Dominique: remove confusing variable reset to 0]

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  19. CVE-2024-56701

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore

    In the Linux kernel, the following vulnerability has been resolved: powerpc/pseries: Fix dtl_access_lock to be a rw_semaphore The dtl_access_lock needs to be a rw_sempahore, a sleeping lock, because the code calls kmalloc() while holding it, which can sleep: # echo 1 > /proc/powerpc/vcpudispatch_stats BUG: sleeping function called from invalid context at include/linux/sched/mm.h:337 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 199, name: sh preempt_count: 1, expected: 0 3 locks held by sh/199: #0: c00000000a0743f8 (sb_writers#3){.+.+}-{0:0}, at: vfs_write+0x324/0x438 #1: c0000000028c7058 (dtl_enable_mutex){+.+.}-{

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

  20. CVE-2024-56700

    Mittel · CVSS 5.7EPSS 0,22%Korrektur verfügbar

    media: wl128x: Fix atomicity violation in fmc_send_cmd()

    In the Linux kernel, the following vulnerability has been resolved: media: wl128x: Fix atomicity violation in fmc_send_cmd() Atomicity violation occurs when the fmc_send_cmd() function is executed simultaneously with the modification of the fmdev->resp_skb value. Consider a scenario where, after passing the validity check within the function, a non-null fmdev->resp_skb variable is assigned a null value. This results in an invalid fmdev->resp_skb variable passing the validity check. As seen in the later part of the function, skb = fmdev->resp_skb; when the invalid fmdev->resp_skb passes the check, a null pointer dereference error may occur a

    linux-intel-iotg-5.15Betriebssysteme
    • Auf 5.15.0-1077.83~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
    Originalmeldung 1 ↗Originalmeldung 2 ↗Originalmeldung 3 ↗

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →