p PatchFirst

PatchFirst · Свежие уязвимости

Уязвимости linux-lowlatency-hwe-5.15 · Страница 177

За последние 30 дней в linux-lowlatency-hwe-5.15 опубликовано уязвимостей: 0; в каталоге KEV: 0.

Фильтры уязвимостей
Сбросить фильтры

Уязвимостей: 4513

  1. CVE-2024-35936

    Средний · CVSS 5.5EPSS 0,23%Есть исправление

    btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks()

    In the Linux kernel, the following vulnerability has been resolved: btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() The unhandled case in btrfs_relocate_sys_chunks() loop is a corruption, as it could be caused only by two impossible conditions: - at first the search key is set up to look for a chunk tree item, with offset -1, this is an inexact search and the key->offset will contain the correct offset upon a successful search, a valid chunk tree item cannot have an offset -1 - after first successful search, the found_key corresponds to a chunk item, the offset is decremented by 1 before the next loop, it's

    • Обновитесь до 5.15.0-116.126~20.04.1
  2. CVE-2024-35935

    Низкий · CVSS 3.3EPSS 0,22%Есть исправление

    btrfs: send: handle path ref underflow in header iterate_inode_ref()

    In the Linux kernel, the following vulnerability has been resolved: btrfs: send: handle path ref underflow in header iterate_inode_ref() Change BUG_ON to proper error handling if building the path buffer fails. The pointers are not printed so we don't accidentally leak kernel addresses.

    • Обновитесь до 5.15.0-116.126~20.04.1
  3. CVE-2024-35934

    Средний · CVSS 6.8EPSS 0,21%Есть исправление

    net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list()

    In the Linux kernel, the following vulnerability has been resolved: net/smc: reduce rtnl pressure in smc_pnet_create_pnetids_list() Many syzbot reports show extreme rtnl pressure, and many of them hint that smc acquires rtnl in netns creation for no good reason [1] This patch returns early from smc_pnet_net_init() if there is no netdevice yet. I am not even sure why smc_pnet_create_pnetids_list() even exists, because smc_pnet_netdev_event() is also calling smc_pnet_add_base_pnetid() when handling NETDEV_UP event. [1] extract of typical syzbot reports 2 locks held by syz-executor.3/12252: #0: ffffffff8f369610 (pernet_ops_rwsem){++++}-{

    • Обновитесь до 5.15.0-116.126~20.04.1
  4. CVE-2024-35930

    Средний · CVSS 5.5EPSS 0,22%Есть исправление

    scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc()

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix possible memory leak in lpfc_rcv_padisc() The call to lpfc_sli4_resume_rpi() in lpfc_rcv_padisc() may return an unsuccessful status. In such cases, the elsiocb is not issued, the completion is not called, and thus the elsiocb resource is leaked. Check return value after calling lpfc_sli4_resume_rpi() and conditionally release the elsiocb resource.

    • Обновитесь до 5.15.0-116.126~20.04.1
  5. CVE-2024-35925

    Средний · CVSS 5.5EPSS 0,23%Есть исправление

    block: prevent division by zero in blk_rq_stat_sum()

    In the Linux kernel, the following vulnerability has been resolved: block: prevent division by zero in blk_rq_stat_sum() The expression dst->nr_samples + src->nr_samples may have zero value on overflow. It is necessary to add a check to avoid division by zero. Found by Linux Verification Center (linuxtesting.org) with Svace.

    • Обновитесь до 5.15.0-116.126~20.04.1
  6. CVE-2024-35922

    Средний · CVSS 5.5EPSS 0,22%Есть исправление

    fbmon: prevent division by zero in fb_videomode_from_videomode()

    In the Linux kernel, the following vulnerability has been resolved: fbmon: prevent division by zero in fb_videomode_from_videomode() The expression htotal * vtotal can have a zero value on overflow. It is necessary to prevent division by zero like in fb_var_to_videomode(). Found by Linux Verification Center (linuxtesting.org) with Svace.

    • Обновитесь до 5.15.0-116.126~20.04.1
  7. CVE-2023-52699

    Средний · CVSS 5.3EPSS 0,97%Есть исправление

    sysv: don't call sb_bread() with pointers_lock held

    In the Linux kernel, the following vulnerability has been resolved: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_

    • Обновитесь до 5.15.0-116.126~20.04.1
  8. CVE-2024-35915

    Высокий · CVSS 8.8EPSS 0,32%Есть исправление

    nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet

    In the Linux kernel, the following vulnerability has been resolved: nfc: nci: Fix uninit-value in nci_dev_up and nci_ntf_packet syzbot reported the following uninit-value access issue [1][2]: nci_rx_work() parses and processes received packet. When the payload length is zero, each message type handler reads uninitialized payload and KMSAN detects this issue. The receipt of a packet with a zero-size payload is considered unexpected, and therefore, such packets should be silently discarded. This patch resolved this issue by checking payload size before calling each message type handler codes.

    • Обновитесь до 5.15.0-116.126~20.04.1
  9. CVE-2024-35912

    Средний · CVSS 5.5EPSS 0,21%Есть исправление

    wifi: iwlwifi: mvm: rfi: fix potential response leaks

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: rfi: fix potential response leaks If the rx payload length check fails, or if kmemdup() fails, we still need to free the command response. Fix that.

    • Обновитесь до 5.15.0-116.126~20.04.1
  10. CVE-2024-35910

    Высокий · CVSS 7.8EPSS 0,26%Есть исправление

    tcp: properly terminate timers for kernel sockets

    In the Linux kernel, the following vulnerability has been resolved: tcp: properly terminate timers for kernel sockets We had various syzbot reports about tcp timers firing after the corresponding netns has been dismantled. Fortunately Josef Bacik could trigger the issue more often, and could test a patch I wrote two years ago. When TCP sockets are closed, we call inet_csk_clear_xmit_timers() to 'stop' the timers. inet_csk_clear_xmit_timers() can be called from any context, including when socket lock is held. This is the reason it uses sk_stop_timer(), aka del_timer(). This means that ongoing timers might finish much later. For user sock

    • Обновитесь до 5.15.0-116.126~20.04.1
  11. CVE-2024-35907

    Средний · CVSS 5.5EPSS 0,23%Есть исправление

    mlxbf_gige: call request_irq() after NAPI initialized

    In the Linux kernel, the following vulnerability has been resolved: mlxbf_gige: call request_irq() after NAPI initialized The mlxbf_gige driver encounters a NULL pointer exception in mlxbf_gige_open() when kdump is enabled. The sequence to reproduce the exception is as follows: a) enable kdump b) trigger kdump via "echo c > /proc/sysrq-trigger" c) kdump kernel executes d) kdump kernel loads mlxbf_gige module e) the mlxbf_gige module runs its open() as the the "oob_net0" interface is brought up f) mlxbf_gige module will experience an exception during its open(), something like: Unable to handle kernel NULL pointer dereference at

    • Обновитесь до 5.15.0-116.126~20.04.1
  12. CVE-2024-35905

    Высокий · CVSS 7.8EPSS 0,22%Есть исправление

    bpf: Protect against int overflow for stack access size

    In the Linux kernel, the following vulnerability has been resolved: bpf: Protect against int overflow for stack access size This patch re-introduces protection against the size of access to stack memory being negative; the access size can appear negative as a result of overflowing its signed int representation. This should not actually happen, as there are other protections along the way, but we should protect against it anyway. One code path was missing such protections (fixed in the previous patch in the series), causing out-of-bounds array accesses in check_stack_range_initialized(). This patch causes the verification of a program with s

    • Обновитесь до 5.15.0-116.126~20.04.1
  13. CVE-2024-35904

    Средний · CVSS 5.5EPSS 0,23%Есть исправление

    selinux: avoid dereference of garbage after mount failure

    In the Linux kernel, the following vulnerability has been resolved: selinux: avoid dereference of garbage after mount failure In case kern_mount() fails and returns an error pointer return in the error branch instead of continuing and dereferencing the error pointer. While on it drop the never read static variable selinuxfs_mount.

    • Обновитесь до 5.15.0-127.137~20.04.1
  14. CVE-2024-35902

    Средний · CVSS 5.5EPSS 0,22%Есть исправление

    net/rds: fix possible cp null dereference

    In the Linux kernel, the following vulnerability has been resolved: net/rds: fix possible cp null dereference cp might be null, calling cp->cp_conn would produce null dereference [Simon Horman adds:] Analysis: * cp is a parameter of __rds_rdma_map and is not reassigned. * The following call-sites pass a NULL cp argument to __rds_rdma_map() - rds_get_mr() - rds_get_mr_for_dest * Prior to the code above, the following assumes that cp may be NULL (which is indicative, but could itself be unnecessary) trans_private = rs->rs_transport->get_mr( sg, nents, rs, &mr->r_key, cp ? cp->cp_conn : NULL, args->vec.addr, args->vec.bytes,

    • Обновитесь до 5.15.0-116.126~20.04.1
  15. CVE-2024-35900

    Средний · CVSS 6.8EPSS 0,23%Есть исправление

    netfilter: nf_tables: reject new basechain after table flag update

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: reject new basechain after table flag update When dormant flag is toggled, hooks are disabled in the commit phase by iterating over current chains in table (existing and new). The following configuration allows for an inconsistent state: add table x add chain x y { type filter hook input priority 0; } add table x { flags dormant; } add chain x w { type filter hook input priority 1; } which triggers the following warning when trying to unregister chain w which is already unregistered. [ 127.322252] WARNING: CPU: 7 PID: 1211 at net/netfilter

    • Обновитесь до 5.15.0-116.126~20.04.1
  16. CVE-2024-35899

    Высокий · CVSS 7.3EPSS 0,2%Есть исправление

    netfilter: nf_tables: flush pending destroy work before exit_net release

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: flush pending destroy work before exit_net release Similar to 2c9f0293280e ("netfilter: nf_tables: flush pending destroy work before netlink notifier") to address a race between exit_net and the destroy workqueue. The trace below shows an element to be released via destroy workqueue while exit_net path (triggered via module removal) has already released the set that is used in such transaction. [ 1360.547789] BUG: KASAN: slab-use-after-free in nf_tables_trans_destroy_work+0x3f5/0x590 [nf_tables] [ 1360.547861] Read of size 8 at addr ffff888140500cc0

    • Обновитесь до 5.15.0-116.126~20.04.1
  17. CVE-2024-35898

    Высокий · CVSS 7EPSS 0,2%Есть исправление

    netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get()

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_flowtable_type_get() nft_unregister_flowtable_type() within nf_flow_inet_module_exit() can concurrent with __nft_flowtable_type_get() within nf_tables_newflowtable(). And thhere is not any protection when iterate over nf_tables_flowtables list in __nft_flowtable_type_get(). Therefore, there is pertential data-race of nf_tables_flowtables list entry. Use list_for_each_entry_rcu() to iterate over nf_tables_flowtables list in __nft_flowtable_type_get(), and use rcu_read_lock() in the caller nft_flowtable_type_get() to pro

    • Обновитесь до 5.15.0-116.126~20.04.1
  18. CVE-2024-35897

    Высокий · CVSS 7.8EPSS 0,25%Есть исправление

    netfilter: nf_tables: discard table flag update with pending basechain deletion

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: discard table flag update with pending basechain deletion Hook unregistration is deferred to the commit phase, same occurs with hook updates triggered by the table dormant flag. When both commands are combined, this results in deleting a basechain while leaving its hook still registered in the core.

    • Обновитесь до 5.15.0-116.126~20.04.1
  19. CVE-2024-35896

    Высокий · CVSS 7.1EPSS 0,23%Есть исправление

    netfilter: validate user input for expected length

    In the Linux kernel, the following vulnerability has been resolved: netfilter: validate user input for expected length I got multiple syzbot reports showing old bugs exposed by BPF after commit 20f2505fb436 ("bpf: Try to avoid kzalloc in cgroup/{s,g}etsockopt") setsockopt() @optlen argument should be taken into account before copying data. BUG: KASAN: slab-out-of-bounds in copy_from_sockptr_offset include/linux/sockptr.h:49 [inline] BUG: KASAN: slab-out-of-bounds in copy_from_sockptr include/linux/sockptr.h:55 [inline] BUG: KASAN: slab-out-of-bounds in do_replace net/ipv4/netfilter/ip_tables.c:1111 [inline] BUG: KASAN: slab-out-of-bou

    • Обновитесь до 5.15.0-116.126~20.04.1
  20. CVE-2024-35895

    Средний · CVSS 5.6EPSS 0,18%Есть исправление

    bpf, sockmap: Prevent lock inversion deadlock in map delete elem

    In the Linux kernel, the following vulnerability has been resolved: bpf, sockmap: Prevent lock inversion deadlock in map delete elem syzkaller started using corpuses where a BPF tracing program deletes elements from a sockmap/sockhash map. Because BPF tracing programs can be invoked from any interrupt context, locks taken during a map_delete_elem operation must be hardirq-safe. Otherwise a deadlock due to lock inversion is possible, as reported by lockdep: CPU0 CPU1 ---- ---- lock(&htab->buckets[i].lock); local_irq_disable();

    • Обновитесь до 5.15.0-116.126~20.04.1

Проверьте свой сервер

Сопоставьте установленный стек и версии со свежими базами уязвимостей.

Проверьте свой сервер →