p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

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

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-2024-26793

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

    gtp: fix use-after-free and null-ptr-deref in gtp_newlink()

    In the Linux kernel, the following vulnerability has been resolved: gtp: fix use-after-free and null-ptr-deref in gtp_newlink() The gtp_link_ops operations structure for the subsystem must be registered after registering the gtp_net_ops pernet operations structure. Syzkaller hit 'general protection fault in gtp_genl_dump_pdp' bug: [ 1010.702740] gtp: GTP module unloaded [ 1010.715877] general protection fault, probably for non-canonical address 0xdffffc0000000001: 0000 [#1] SMP KASAN NOPTI [ 1010.715888] KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f] [ 1010.715895] CPU: 1 PID: 128616 Comm: a.out Not tainted 6.8.0-r

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-26792

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

    btrfs: fix double free of anonymous device after snapshot creation failure

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix double free of anonymous device after snapshot creation failure When creating a snapshot we may do a double free of an anonymous device in case there's an error committing the transaction. The second free may result in freeing an anonymous device number that was allocated by some other subsystem in the kernel or another btrfs filesystem. The steps that lead to this: 1) At ioctl.c:create_snapshot() we allocate an anonymous device number and assign it to pending_snapshot->anon_dev; 2) Then we call btrfs_commit_transaction() and end up at transaction.c:crea

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

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

    btrfs: dev-replace: properly validate device names

    In the Linux kernel, the following vulnerability has been resolved: btrfs: dev-replace: properly validate device names There's a syzbot report that device name buffers passed to device replace are not properly checked for string termination which could lead to a read out of bounds in getname_kernel(). Add a helper that validates both source and target device name buffers. For devid as the source initialize the buffer to empty string in case something tries to read it later. This was originally analyzed and fixed in a different way by Edward Adam Davis (see links).

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-26790

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

    dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-qdma: fix SoC may hang on 16 byte unaligned read There is chip (ls1028a) errata: The SoC may hang on 16 byte unaligned read transactions by QDMA. Unaligned read transactions initiated by QDMA may stall in the NOC (Network On-Chip), causing a deadlock condition. Stalled transactions will trigger completion timeouts in PCIe controller. Workaround: Enable prefetch by setting the source descriptor prefetchable bit ( SD[PF] = 1 ). Implement this workaround.

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

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

    dmaengine: fsl-qdma: init irq after reg initialization

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: fsl-qdma: init irq after reg initialization Initialize the qDMA irqs after the registers are configured so that interrupts that may have been pending from a primary kernel don't get processed by the irq handler before it is ready to and cause panic with the following trace: Call trace: fsl_qdma_queue_handler+0xf8/0x3e8 __handle_irq_event_percpu+0x78/0x2b0 handle_irq_event_percpu+0x1c/0x68 handle_irq_event+0x44/0x78 handle_fasteoi_irq+0xc8/0x178 generic_handle_irq+0x24/0x38 __handle_domain_irq+0x90/0x100 gic_handle_irq+0x5c/0xb8 el1_i

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2024-26787

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

    mmc: mmci: stm32: fix DMA API overlapping mappings warning

    In the Linux kernel, the following vulnerability has been resolved: mmc: mmci: stm32: fix DMA API overlapping mappings warning Turning on CONFIG_DMA_API_DEBUG_SG results in the following warning: DMA-API: mmci-pl18x 48220000.mmc: cacheline tracking EEXIST, overlapping mappings aren't supported WARNING: CPU: 1 PID: 51 at kernel/dma/debug.c:568 add_dma_entry+0x234/0x2f4 Modules linked in: CPU: 1 PID: 51 Comm: kworker/1:2 Not tainted 6.1.28 #1 Hardware name: STMicroelectronics STM32MP257F-EV1 Evaluation Board (DT) Workqueue: events_freezable mmc_rescan Call trace: add_dma_entry+0x234/0x2f4 debug_dma_map_sg+0x198/0x350 __dma_map_sg_attrs+0xa0/

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2024-26782

    Kritisch · CVSS 9.8EPSS 0,72%Korrektur verfügbar

    mptcp: fix double-free on socket dismantle

    In the Linux kernel, the following vulnerability has been resolved: mptcp: fix double-free on socket dismantle when MPTCP server accepts an incoming connection, it clones its listener socket. However, the pointer to 'inet_opt' for the new socket has the same value as the original one: as a consequence, on program exit it's possible to observe the following splat: BUG: KASAN: double-free in inet_sock_destruct+0x54f/0x8b0 Free of addr ffff888485950880 by task swapper/25/0 CPU: 25 PID: 0 Comm: swapper/25 Kdump: loaded Not tainted 6.8.0-rc1+ #609 Hardware name: Supermicro SYS-6027R-72RF/X9DRH-7TF/7F/iTF/iF, BIOS 3.0 07/26/2013 Call

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2024-26750

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

    af_unix: Drop oob_skb ref before purging queue in GC.

    In the Linux kernel, the following vulnerability has been resolved: af_unix: Drop oob_skb ref before purging queue in GC. syzbot reported another task hung in __unix_gc(). [0] The current while loop assumes that all of the left candidates have oob_skb and calling kfree_skb(oob_skb) releases the remaining candidates. However, I missed a case that oob_skb has self-referencing fd and another fd and the latter sk is placed before the former in the candidate list. Then, the while loop never proceeds, resulting the task hung. __unix_gc() has the same loop just before purging the collected skb, so we can call kfree_skb(oob_skb) there and let

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2024-26779

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

    wifi: mac80211: fix race condition on enabling fast-xmit

    In the Linux kernel, the following vulnerability has been resolved: wifi: mac80211: fix race condition on enabling fast-xmit fast-xmit must only be enabled after the sta has been uploaded to the driver, otherwise it could end up passing the not-yet-uploaded sta via drv_tx calls to the driver, leading to potential crashes because of uninitialized drv_priv data. Add a missing sta->uploaded check and re-check fast xmit after inserting a sta.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2024-26778

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

    fbdev: savage: Error out if pixclock equals zero

    In the Linux kernel, the following vulnerability has been resolved: fbdev: savage: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero error. Although pixclock is checked in savagefb_decode_var(), but it is not checked properly in savagefb_probe(). Fix this by checking whether pixclock is zero in the function savagefb_check_var() before info->var.pixclock is used as the divisor. This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2024-26777

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

    fbdev: sis: Error out if pixclock equals zero

    In the Linux kernel, the following vulnerability has been resolved: fbdev: sis: Error out if pixclock equals zero The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero error. In sisfb_check_var(), var->pixclock is used as a divisor to caculate drate before it is checked against zero. Fix this by checking it at the beginning. This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2024-26776

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

    spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected

    In the Linux kernel, the following vulnerability has been resolved: spi: hisi-sfc-v3xx: Return IRQ_NONE if no interrupts were detected Return IRQ_NONE from the interrupt handler when no interrupt was detected. Because an empty interrupt will cause a null pointer error: Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Call trace: complete+0x54/0x100 hisi_sfc_v3xx_isr+0x2c/0x40 [spi_hisi_sfc_v3xx] __handle_irq_event_percpu+0x64/0x1e0 handle_irq_event+0x7c/0x1cc

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2024-26773

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

    ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found()

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocating blocks from corrupted group in ext4_mb_try_best_found() Determine if the group block bitmap is corrupted before using ac_b_ex in ext4_mb_try_best_found() to avoid allocating blocks from a group with a corrupted block bitmap in the following concurrency and making the situation worse. ext4_mb_regular_allocator ext4_lock_group(sb, group) ext4_mb_good_group // check if the group bbitmap is corrupted ext4_mb_complex_scan_group // Scan group gets ac_b_ex but doesn't use it ext4_unlock_group(sb, group) ext4_mark_gro

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2024-26772

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

    ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal()

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid allocating blocks from corrupted group in ext4_mb_find_by_goal() Places the logic for checking if the group's block bitmap is corrupt under the protection of the group lock to avoid allocating blocks from the group with a corrupted block bitmap.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2024-26771

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

    dmaengine: ti: edma: Add some null pointer checks to the edma_probe

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: ti: edma: Add some null pointer checks to the edma_probe devm_kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the pointer validity.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2024-26769

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

    nvmet-fc: avoid deadlock on delete association path

    In the Linux kernel, the following vulnerability has been resolved: nvmet-fc: avoid deadlock on delete association path When deleting an association the shutdown path is deadlocking because we try to flush the nvmet_wq nested. Avoid this by deadlock by deferring the put work into its own work item.

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2024-26766

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

    IB/hfi1: Fix sdma.h tx->num_descs off-by-one error

    In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix sdma.h tx->num_descs off-by-one error Unfortunately the commit `fd8958efe877` introduced another error causing the `descs` array to overflow. This reults in further crashes easily reproducible by `sendmsg` system call. [ 1080.836473] general protection fault, probably for non-canonical address 0x400300015528b00a: 0000 [#1] PREEMPT SMP PTI [ 1080.869326] RIP: 0010:hfi1_ipoib_build_ib_tx_headers.constprop.0+0xe1/0x2b0 [hfi1] -- [ 1080.974535] Call Trace: [ 1080.976990] <TASK> [ 1081.021929] hfi1_ipoib_send_dma_common+0x7a/0x2e0 [hfi1] [ 1081.027364] hfi1_ipoi

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2024-26764

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

    fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio

    In the Linux kernel, the following vulnerability has been resolved: fs/aio: Restrict kiocb_set_cancel_fn() to I/O submitted via libaio If kiocb_set_cancel_fn() is called for I/O submitted via io_uring, the following kernel warning appears: WARNING: CPU: 3 PID: 368 at fs/aio.c:598 kiocb_set_cancel_fn+0x9c/0xa8 Call trace: kiocb_set_cancel_fn+0x9c/0xa8 ffs_epfile_read_iter+0x144/0x1d0 io_read+0x19c/0x498 io_issue_sqe+0x118/0x27c io_submit_sqes+0x25c/0x5fc __arm64_sys_io_uring_enter+0x104/0xab0 invoke_syscall+0x58/0x11c el0_svc_common+0xb4/0xf4 do_el0_svc+0x2c/0xb0 el0_svc+0x2c/0xa4 el0t_64_sync_handler+0x68/0xb4 el0t_64_sync+0x1a

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2024-26763

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

    dm-crypt: don't modify the data when using authenticated encryption

    In the Linux kernel, the following vulnerability has been resolved: dm-crypt: don't modify the data when using authenticated encryption It was said that authenticated encryption could produce invalid tag when the data that is being encrypted is modified [1]. So, fix this problem by copying the data into the clone bio first and then encrypt them inside the clone bio. This may reduce performance, but it is needed to prevent the user from corrupting the device by writing data with O_DIRECT and modifying them at the same time. [1] https://lore.kernel.org/all/[email protected]/T/

    • Auf 5.15.0-1063.69~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2024-26754

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

    gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp()

    In the Linux kernel, the following vulnerability has been resolved: gtp: fix use-after-free and null-ptr-deref in gtp_genl_dump_pdp() The gtp_net_ops pernet operations structure for the subsystem must be registered before registering the generic netlink family. Syzkaller hit 'general protection fault in gtp_genl_dump_pdp' bug: general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN NOPTI KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 PID: 5826 Comm: gtp Not tainted 6.8.0-rc3-std-def-alt1 #1 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.0-al

    • Auf 5.15.0-1063.69~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 →