p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

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

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-26704

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

    ext4: fix double-free of blocks due to wrong extents moved_len

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix double-free of blocks due to wrong extents moved_len In ext4_move_extents(), moved_len is only updated when all moves are successfully executed, and only discards orig_inode and donor_inode preallocations when moved_len is not zero. When the loop fails to exit after successfully moving some extents, moved_len is not updated and remains at 0, so it does not discard the preallocations. If the moved extents overlap with the preallocated extents, the overlapped extents are freed twice in ext4_mb_release_inode_pa() and ext4_process_freed_data() (as described in commit

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-26702

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

    iio: magnetometer: rm3100: add boundary check for the value read from RM3100_REG_TMRC

    In the Linux kernel, the following vulnerability has been resolved: iio: magnetometer: rm3100: add boundary check for the value read from RM3100_REG_TMRC Recently, we encounter kernel crash in function rm3100_common_probe caused by out of bound access of array rm3100_samp_rates (because of underlying hardware failures). Add boundary check to prevent out of bound access.

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2024-26698

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

    hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove

    In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: Fix race condition between netvsc_probe and netvsc_remove In commit ac5047671758 ("hv_netvsc: Disable NAPI before closing the VMBus channel"), napi_disable was getting called for all channels, including all subchannels without confirming if they are enabled or not. This caused hv_netvsc getting hung at napi_disable, when netvsc_probe() has finished running but nvdev->subchan_work has not started yet. netvsc_subchan_work() -> rndis_set_subchannel() has not created the sub-channels and because of that netvsc_sc_open() is not running. netvsc_remove() calls cancel_w

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2024-26697

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

    nilfs2: fix data corruption in dsync block recovery for small block sizes

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix data corruption in dsync block recovery for small block sizes The helper function nilfs_recovery_copy_block() of nilfs_recovery_dsync_blocks(), which recovers data from logs created by data sync writes during a mount after an unclean shutdown, incorrectly calculates the on-page offset when copying repair data to the file's page cache. In environments where the block size is smaller than the page size, this flaw can cause data corruption and leak uninitialized memory bytes during the recovery process. Fix these issues by correcting this byte offset calculation

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2024-26696

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

    nilfs2: fix hang in nilfs_lookup_dirty_data_buffers()

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix hang in nilfs_lookup_dirty_data_buffers() Syzbot reported a hang issue in migrate_pages_batch() called by mbind() and nilfs_lookup_dirty_data_buffers() called in the log writer of nilfs2. While migrate_pages_batch() locks a folio and waits for the writeback to complete, the log writer thread that should bring the writeback to completion picks up the folio being written back in nilfs_lookup_dirty_data_buffers() that it calls for subsequent log creation and was trying to lock the folio. Thus causing a deadlock. In the first place, it is unexpected that folios/p

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2024-26695

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

    crypto: ccp - Fix null pointer dereference in __sev_platform_shutdown_locked

    In the Linux kernel, the following vulnerability has been resolved: crypto: ccp - Fix null pointer dereference in __sev_platform_shutdown_locked The SEV platform device can be shutdown with a null psp_master, e.g., using DEBUG_TEST_DRIVER_REMOVE. Found using KASAN: [ 137.148210] ccp 0000:23:00.1: enabling device (0000 -> 0002) [ 137.162647] ccp 0000:23:00.1: no command queues available [ 137.170598] ccp 0000:23:00.1: sev enabled [ 137.174645] ccp 0000:23:00.1: psp enabled [ 137.178890] general protection fault, probably for non-canonical address 0xdffffc000000001e: 0000 [#1] PREEMPT SMP DEBUG_PAGEALLOC KASAN NOPTI [ 137.182693] KASA

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2024-26689

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

    ceph: prevent use-after-free in encode_cap_msg()

    In the Linux kernel, the following vulnerability has been resolved: ceph: prevent use-after-free in encode_cap_msg() In fs/ceph/caps.c, in encode_cap_msg(), "use after free" error was caught by KASAN at this line - 'ceph_buffer_get(arg->xattr_buf);'. This implies before the refcount could be increment here, it was freed. In same file, in "handle_cap_grant()" refcount is decremented by this line - 'ceph_buffer_put(ci->i_xattrs.blob);'. It appears that a race occurred and resource was freed by the latter line before the former line could increment it. encode_cap_msg() is called by __send_cap() and __send_cap() is called by ceph_check_caps()

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2024-26688

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

    fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super

    In the Linux kernel, the following vulnerability has been resolved: fs,hugetlb: fix NULL pointer dereference in hugetlbs_fill_super When configuring a hugetlb filesystem via the fsconfig() syscall, there is a possible NULL dereference in hugetlbfs_fill_super() caused by assigning NULL to ctx->hstate in hugetlbfs_parse_param() when the requested pagesize is non valid. E.g: Taking the following steps: fd = fsopen("hugetlbfs", FSOPEN_CLOEXEC); fsconfig(fd, FSCONFIG_SET_STRING, "pagesize", "1024", 0); fsconfig(fd, FSCONFIG_CMD_CREATE, NULL, NULL, 0); Given that the requested "pagesize" is invalid, ctxt->hstate will be replaced

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

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

    xen/events: close evtchn after mapping cleanup

    In the Linux kernel, the following vulnerability has been resolved: xen/events: close evtchn after mapping cleanup shutdown_pirq and startup_pirq are not taking the irq_mapping_update_lock because they can't due to lock inversion. Both are called with the irq_desc->lock being taking. The lock order, however, is first irq_mapping_update_lock and then irq_desc->lock. This opens multiple races: - shutdown_pirq can be interrupted by a function that allocates an event channel: CPU0 CPU1 shutdown_pirq { xen_evtchn_close(e) __startup_pirq { EVTCHNOP_bi

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

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

    nilfs2: fix potential bug in end_buffer_async_write

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential bug in end_buffer_async_write According to a syzbot report, end_buffer_async_write(), which handles the completion of block device writes, may detect abnormal condition of the buffer async_write flag and cause a BUG_ON failure when using nilfs2. Nilfs2 itself does not use end_buffer_async_write(). But, the async_write flag is now used as a marker by commit 7f42ec394156 ("nilfs2: fix issue with race condition of competition between segments for dirty blocks") as a means of resolving double list insertion of dirty blocks in nilfs_lookup_dirty_data_buff

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2023-52639

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

    KVM: s390: vsie: fix race during shadow creation

    In the Linux kernel, the following vulnerability has been resolved: KVM: s390: vsie: fix race during shadow creation Right now it is possible to see gmap->private being zero in kvm_s390_vsie_gmap_notifier resulting in a crash. This is due to the fact that we add gmap->private == kvm after creation: static int acquire_gmap_shadow(struct kvm_vcpu *vcpu, struct vsie_page *vsie_page) { [...] gmap = gmap_shadow(vcpu->arch.gmap, asce, edat); if (IS_ERR(gmap)) return PTR_ERR(gmap); gmap->private = vcpu->kvm; Let children inherit the private field of the parent.

    • Auf 5.15.0-1073.79~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2023-52638

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

    can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock

    In the Linux kernel, the following vulnerability has been resolved: can: j1939: prevent deadlock by changing j1939_socks_lock to rwlock The following 3 locks would race against each other, causing the deadlock situation in the Syzbot bug report: - j1939_socks_lock - active_session_list_lock - sk_session_queue_lock A reasonable fix is to change j1939_socks_lock to an rwlock, since in the rare situations where a write lock is required for the linked list that j1939_socks_lock is protecting, the code does not attempt to acquire any more locks. This would break the circular lock dependency, where, for example, the current thread already locks

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2023-52637

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

    can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER)

    In the Linux kernel, the following vulnerability has been resolved: can: j1939: Fix UAF in j1939_sk_match_filter during setsockopt(SO_J1939_FILTER) Lock jsk->sk to prevent UAF when setsockopt(..., SO_J1939_FILTER, ...) modifies jsk->filters while receiving packets. Following trace was seen on affected system: ================================================================== BUG: KASAN: slab-use-after-free in j1939_sk_recv_match_one+0x1af/0x2d0 [can_j1939] Read of size 4 at addr ffff888012144014 by task j1939/350 CPU: 0 PID: 350 Comm: j1939 Tainted: G W OE 6.5.0-rc5 #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2024-26684

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

    net: stmmac: xgmac: fix handling of DPP safety error for DMA channels

    In the Linux kernel, the following vulnerability has been resolved: net: stmmac: xgmac: fix handling of DPP safety error for DMA channels Commit 56e58d6c8a56 ("net: stmmac: Implement Safety Features in XGMAC core") checks and reports safety errors, but leaves the Data Path Parity Errors for each channel in DMA unhandled at all, lead to a storm of interrupt. Fix it by checking and clearing the DMA_DPP_Interrupt_Status register.

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2024-26680

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

    net: atlantic: Fix DMA mapping for PTP hwts ring

    In the Linux kernel, the following vulnerability has been resolved: net: atlantic: Fix DMA mapping for PTP hwts ring Function aq_ring_hwts_rx_alloc() maps extra AQ_CFG_RXDS_DEF bytes for PTP HWTS ring but then generic aq_ring_free() does not take this into account. Create and use a specific function to free HWTS ring to fix this issue. Trace: [ 215.351607] ------------[ cut here ]------------ [ 215.351612] DMA-API: atlantic 0000:4b:00.0: device driver frees DMA memory with different size [device address=0x00000000fbdd0000] [map size=34816 bytes] [unmap size=32768 bytes] [ 215.351635] WARNING: CPU: 33 PID: 10759 at kernel/dma/debug.c:988

    • Auf 5.15.0-1068.74~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2024-26679

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

    inet: read sk->sk_family once in inet_recv_error()

    In the Linux kernel, the following vulnerability has been resolved: inet: read sk->sk_family once in inet_recv_error() inet_recv_error() is called without holding the socket lock. IPv6 socket could mutate to IPv4 with IPV6_ADDRFORM socket option and trigger a KCSAN warning.

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2024-26677

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

    rxrpc: Fix delayed ACKs to not set the reference serial number

    In the Linux kernel, the following vulnerability has been resolved: rxrpc: Fix delayed ACKs to not set the reference serial number Fix the construction of delayed ACKs to not set the reference serial number as they can't be used as an RTT reference.

    • Auf 5.15.0-1070.76~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2024-26676

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

    af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC.

    In the Linux kernel, the following vulnerability has been resolved: af_unix: Call kfree_skb() for dead unix_(sk)->oob_skb in GC. syzbot reported a warning [0] in __unix_gc() with a repro, which creates a socketpair and sends one socket's fd to itself using the peer. socketpair(AF_UNIX, SOCK_STREAM, 0, [3, 4]) = 0 sendmsg(4, {msg_name=NULL, msg_namelen=0, msg_iov=[{iov_base="\360", iov_len=1}], msg_iovlen=1, msg_control=[{cmsg_len=20, cmsg_level=SOL_SOCKET, cmsg_type=SCM_RIGHTS, cmsg_data=[3]}], msg_controllen=24, msg_flags=0}, MSG_OOB|MSG_PROBE|MSG_DONTWAIT|MSG_ZEROCOPY) = 1 Th

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2024-26675

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

    ppp_async: limit MRU to 64K

    In the Linux kernel, the following vulnerability has been resolved: ppp_async: limit MRU to 64K syzbot triggered a warning [1] in __alloc_pages(): WARN_ON_ONCE_GFP(order > MAX_PAGE_ORDER, gfp) Willem fixed a similar issue in commit c0a2a1b0d631 ("ppp: limit MRU to 64K") Adopt the same sanity check for ppp_async_ioctl(PPPIOCSMRU) [1]: WARNING: CPU: 1 PID: 11 at mm/page_alloc.c:4543 __alloc_pages+0x308/0x698 mm/page_alloc.c:4543 Modules linked in: CPU: 1 PID: 11 Comm: kworker/u4:0 Not tainted 6.8.0-rc2-syzkaller-g41bccc98fb79 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023 Workqueue: events_u

    • Auf 5.15.0-1061.67~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2024-26673

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

    netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_ct: sanitize layer 3 and 4 protocol number in custom expectations - Disallow families other than NFPROTO_{IPV4,IPV6,INET}. - Disallow layer 4 protocol with no ports, since destination port is a mandatory attribute for this object.

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