p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-aws-5.15 · Seite 169

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4238

  1. CVE-2023-52664

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

    net: atlantic: eliminate double free in error handling logic

    In the Linux kernel, the following vulnerability has been resolved: net: atlantic: eliminate double free in error handling logic Driver has a logic leak in ring data allocation/free, where aq_ring_free could be called multiple times on same ring, if system is under stress and got memory allocation error. Ring pointer was used as an indicator of failure, but this is not correct since only ring data is allocated/deallocated. Ring itself is an array member. Changing ring allocation functions to return error code directly. This simplifies error handling and eliminates aq_ring_free on higher layer.

    • Auf 5.15.0-1083.90~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-35830

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

    media: tc358743: register v4l2 async device only after successful setup

    In the Linux kernel, the following vulnerability has been resolved: media: tc358743: register v4l2 async device only after successful setup Ensure the device has been setup correctly before registering the v4l2 async device, thus allowing userspace to access.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2024-35828

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

    wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer()

    In the Linux kernel, the following vulnerability has been resolved: wifi: libertas: fix some memleaks in lbs_allocate_cmd_buffer() In the for statement of lbs_allocate_cmd_buffer(), if the allocation of cmdarray[i].cmdbuf fails, both cmdarray and cmdarray[i].cmdbuf needs to be freed. Otherwise, there will be memleaks in lbs_allocate_cmd_buffer().

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2023-52662

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

    drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node

    In the Linux kernel, the following vulnerability has been resolved: drm/vmwgfx: fix a memleak in vmw_gmrid_man_get_node When ida_alloc_max fails, resources allocated before should be freed, including *res allocated by kmalloc and ttm_resource_init.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2024-35825

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

    usb: gadget: ncm: Fix handling of zero block length packets

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: ncm: Fix handling of zero block length packets While connecting to a Linux host with CDC_NCM_NTB_DEF_SIZE_TX set to 65536, it has been observed that we receive short packets, which come at interval of 5-10 seconds sometimes and have block length zero but still contain 1-2 valid datagrams present. According to the NCM spec: "If wBlockLength = 0x0000, the block is terminated by a short packet. In this case, the USB transfer must still be shorter than dwNtbInMaxSize or dwNtbOutMaxSize. If exactly dwNtbInMaxSize or dwNtbOutMaxSize bytes are sent, and the size is

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2024-35823

    Mittel · CVSS 5.3EPSS 0,92%Korrektur verfügbar

    vt: fix unicode buffer corruption when deleting characters

    In the Linux kernel, the following vulnerability has been resolved: vt: fix unicode buffer corruption when deleting characters This is the same issue that was fixed for the VGA text buffer in commit 39cdb68c64d8 ("vt: fix memory overlapping when deleting chars in the buffer"). The cure is also the same i.e. replace memcpy() with memmove() due to the overlaping buffers.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2024-35822

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

    usb: udc: remove warning when queue disabled ep

    In the Linux kernel, the following vulnerability has been resolved: usb: udc: remove warning when queue disabled ep It is possible trigger below warning message from mass storage function, WARNING: CPU: 6 PID: 3839 at drivers/usb/gadget/udc/core.c:294 usb_ep_queue+0x7c/0x104 pc : usb_ep_queue+0x7c/0x104 lr : fsg_main_thread+0x494/0x1b3c Root cause is mass storage function try to queue request from main thread, but other thread may already disable ep when function disable. As there is no function failure in the driver, in order to avoid effort to fix warning, change WARN_ON_ONCE() in usb_ep_queue() to pr_debug().

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2024-35821

    Hoch · CVSS 7.5EPSS 0,57%Korrektur verfügbar

    ubifs: Set page uptodate in the correct place

    In the Linux kernel, the following vulnerability has been resolved: ubifs: Set page uptodate in the correct place Page cache reads are lockless, so setting the freshly allocated page uptodate before we've overwritten it with the data it's supposed to have in it will allow a simultaneous reader to see old data. Move the call to SetPageUptodate into ubifs_write_end(), which is after we copied the new data into the page.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2024-35819

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

    soc: fsl: qbman: Use raw spinlock for cgr_lock

    In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: Use raw spinlock for cgr_lock smp_call_function always runs its callback in hard IRQ context, even on PREEMPT_RT, where spinlocks can sleep. So we need to use a raw spinlock for cgr_lock to ensure we aren't waiting on a sleeping task. Although this bug has existed for a while, it was not apparent until commit ef2a8d5478b9 ("net: dpaa: Adjust queue depth on rate change") which invokes smp_call_function_single via qman_update_cgr_safe every time a link goes up or down.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2024-35817

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

    drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: amdgpu_ttm_gart_bind set gtt bound flag Otherwise after the GTT bo is released, the GTT and gart space is freed but amdgpu_ttm_backend_unbind will not clear the gart page table entry and leave valid mapping entry pointing to the stale system page. Then if GPU access the gart address mistakely, it will read undefined value instead page fault, harder to debug and reproduce the real issue.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2024-35815

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

    fs/aio: Check IOCB_AIO_RW before the struct aio_kiocb conversion

    In the Linux kernel, the following vulnerability has been resolved: fs/aio: Check IOCB_AIO_RW before the struct aio_kiocb conversion The first kiocb_set_cancel_fn() argument may point at a struct kiocb that is not embedded inside struct aio_kiocb. With the current code, depending on the compiler, the req->ki_ctx read happens either before the IOCB_AIO_RW test or after that test. Move the req->ki_ctx read such that it is guaranteed that the IOCB_AIO_RW test happens first.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2024-35813

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

    mmc: core: Avoid negative index with array access

    In the Linux kernel, the following vulnerability has been resolved: mmc: core: Avoid negative index with array access Commit 4d0c8d0aef63 ("mmc: core: Use mrq.sbc in close-ended ffu") assigns prev_idata = idatas[i - 1], but doesn't check that the iterator i is greater than zero. Let's fix this by adding a check.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2024-35811

    Hoch · CVSS 8.8EPSS 0,35%Korrektur verfügbar

    wifi: brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach

    In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: Fix use-after-free bug in brcmf_cfg80211_detach This is the candidate patch of CVE-2023-47233 : https://nvd.nist.gov/vuln/detail/CVE-2023-47233 In brcm80211 driver,it starts with the following invoking chain to start init a timeout worker: ->brcmf_usb_probe ->brcmf_usb_probe_cb ->brcmf_attach ->brcmf_bus_started ->brcmf_cfg80211_attach ->wl_init_priv ->brcmf_init_escan ->INIT_WORK(&cfg->escan_timeout_work, brcmf_cfg80211_escan_timeout_worker); If we disconnect the USB by hotplug, it will call brc

    • Auf 5.15.0-1062.68~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2024-35809

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

    PCI/PM: Drain runtime-idle callbacks before driver removal

    In the Linux kernel, the following vulnerability has been resolved: PCI/PM: Drain runtime-idle callbacks before driver removal A race condition between the .runtime_idle() callback and the .remove() callback in the rtsx_pcr PCI driver leads to a kernel crash due to an unhandled page fault [1]. The problem is that rtsx_pci_runtime_idle() is not expected to be running after pm_runtime_get_sync() has been called, but the latter doesn't really guarantee that. It only guarantees that the suspend and resume callbacks will not be running when it returns. However, if a .runtime_idle() callback is already running when pm_runtime_get_sync() is cal

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2024-35807

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

    ext4: fix corruption during on-line resize

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix corruption during on-line resize We observed a corruption during on-line resize of a file system that is larger than 16 TiB with 4k block size. With having more then 2^32 blocks resize_inode is turned off by default by mke2fs. The issue can be reproduced on a smaller file system for convenience by explicitly turning off resize_inode. An on-line resize across an 8 GiB boundary (the size of a meta block group in this setup) then leads to a corruption: dev=/dev/<some_dev> # should be >= 16 GiB mkdir -p /corruption /sbin/mke2fs -t ext4 -b 4096 -O ^resize_inode

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2024-35806

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

    soc: fsl: qbman: Always disable interrupts when taking cgr_lock

    In the Linux kernel, the following vulnerability has been resolved: soc: fsl: qbman: Always disable interrupts when taking cgr_lock smp_call_function_single disables IRQs when executing the callback. To prevent deadlocks, we must disable IRQs when taking cgr_lock elsewhere. This is already done by qman_update_cgr and qman_delete_cgr; fix the other lockers.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2024-35805

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

    dm snapshot: fix lockup in dm_exception_table_exit

    In the Linux kernel, the following vulnerability has been resolved: dm snapshot: fix lockup in dm_exception_table_exit There was reported lockup when we exit a snapshot with many exceptions. Fix this by adding "cond_resched" to the loop that frees the exceptions.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2024-35804

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

    KVM: x86: Mark target gfn of emulated atomic instruction as dirty

    In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Mark target gfn of emulated atomic instruction as dirty When emulating an atomic access on behalf of the guest, mark the target gfn dirty if the CMPXCHG by KVM is attempted and doesn't fault. This fixes a bug where KVM effectively corrupts guest memory during live migration by writing to guest memory without informing userspace that the page is dirty. Marking the page dirty got unintentionally dropped when KVM's emulated CMPXCHG was converted to do a user access. Before that, KVM explicitly mapped the guest page into kernel memory, and marked the page dirty dur

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2024-35796

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

    net: ll_temac: platform_get_resource replaced by wrong function

    In the Linux kernel, the following vulnerability has been resolved: net: ll_temac: platform_get_resource replaced by wrong function The function platform_get_resource was replaced with devm_platform_ioremap_resource_byname and is called using 0 as name. This eventually ends up in platform_get_resource_byname in the call stack, where it causes a null pointer in strcmp. if (type == resource_type(r) && !strcmp(r->name, name)) It should have been replaced with devm_platform_ioremap_resource.

    • Auf 5.15.0-1065.71~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

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

Prüfen Sie Ihren Server →