p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-hwe-5.15 · Page n° 169

Vulnérabilité publiée pour linux-hwe-5.15 au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 4389

  1. CVE-2023-52730

    Moyenne · CVSS 5.5EPSS 0,25%Correctif disponible

    mmc: sdio: fix possible resource leaks in some error paths

    In the Linux kernel, the following vulnerability has been resolved: mmc: sdio: fix possible resource leaks in some error paths If sdio_add_func() or sdio_init_func() fails, sdio_remove_func() can not release the resources, because the sdio function is not presented in these two cases, it won't call of_node_put() or put_device(). To fix these leaks, make sdio_func_present() only control whether device_del() needs to be called or not, then always call of_node_put() and put_device(). In error case in sdio_init_func(), the reference of 'card->dev' is not get, to avoid redundant put in sdio_free_func_cis(), move the get_device() to sdio_alloc_

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  2. CVE-2023-52708

    Moyenne · CVSS 5.5EPSS 0,25%Correctif disponible

    mmc: mmc_spi: fix error handling in mmc_spi_probe()

    In the Linux kernel, the following vulnerability has been resolved: mmc: mmc_spi: fix error handling in mmc_spi_probe() If mmc_add_host() fails, it doesn't need to call mmc_remove_host(), or it will cause null-ptr-deref, because of deleting a not added device in mmc_remove_host(). To fix this, goto label 'fail_glue_init', if mmc_add_host() fails, and change the label 'fail_add_host' to 'fail_gpiod_request'.

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  3. CVE-2023-52707

    Élevée · CVSS 7.8EPSS 0,26%Correctif disponible

    sched/psi: Fix use-after-free in ep_remove_wait_queue()

    In the Linux kernel, the following vulnerability has been resolved: sched/psi: Fix use-after-free in ep_remove_wait_queue() If a non-root cgroup gets removed when there is a thread that registered trigger and is polling on a pressure file within the cgroup, the polling waitqueue gets freed in the following path: do_rmdir cgroup_rmdir kernfs_drain_open_files cgroup_file_release cgroup_pressure_release psi_trigger_destroy However, the polling thread still has a reference to the pressure file and will access the freed waitqueue when the file is closed or upon exit: fput ep_eventpoll_release ep_fr

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  4. CVE-2023-52705

    Moyenne · CVSS 5.5EPSS 0,25%Correctif disponible

    nilfs2: fix underflow in second superblock position calculations

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix underflow in second superblock position calculations Macro NILFS_SB2_OFFSET_BYTES, which computes the position of the second superblock, underflows when the argument device size is less than 4096 bytes. Therefore, when using this macro, it is necessary to check in advance that the device size is not less than a lower limit, or at least that underflow does not occur. The current nilfs2 implementation lacks this check, causing out-of-bound block access when mounting devices smaller than 4096 bytes: I/O error, dev loop0, sector 36028797018963960 op 0x0:(READ) f

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  5. CVE-2023-52703

    Faible · CVSS 3.3EPSS 0,25%Correctif disponible

    net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path

    In the Linux kernel, the following vulnerability has been resolved: net/usb: kalmia: Don't pass act_len in usb_bulk_msg error path syzbot reported that act_len in kalmia_send_init_packet() is uninitialized when passing it to the first usb_bulk_msg error path. Jiri Pirko noted that it's pointless to pass it in the error path, and that the value that would be printed in the second error path would be the value of act_len from the first call to usb_bulk_msg.[1] With this in mind, let's just not pass act_len to the usb_bulk_msg error paths. 1: https://lore.kernel.org/lkml/Y9pY61y1nwTuzMOa@nanopsycho/

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  6. CVE-2023-52702

    Moyenne · CVSS 5.5EPSS 0,25%Correctif disponible

    net: openvswitch: fix possible memory leak in ovs_meter_cmd_set()

    In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: fix possible memory leak in ovs_meter_cmd_set() old_meter needs to be free after it is detached regardless of whether the new meter is successfully attached.

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  7. CVE-2022-48708

    Moyenne · CVSS 5.5EPSS 0,24%Correctif disponible

    pinctrl: single: fix potential NULL dereference

    In the Linux kernel, the following vulnerability has been resolved: pinctrl: single: fix potential NULL dereference Added checking of pointer "function" in pcs_set_mux(). pinmux_generic_get_function() can return NULL and the pointer "function" was dereferenced without checking against NULL. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    • Mettez à jour vers 5.15.0-72.79~20.04.1
    Publication Mise à jour
  8. CVE-2024-36008

    Moyenne · CVSS 5.7EPSS 0,21%Correctif disponible

    ipv4: check for NULL idev in ip_route_use_hint()

    In the Linux kernel, the following vulnerability has been resolved: ipv4: check for NULL idev in ip_route_use_hint() syzbot was able to trigger a NULL deref in fib_validate_source() in an old tree [1]. It appears the bug exists in latest trees. All calls to __in_dev_get_rcu() must be checked for a NULL result. [1] general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] CPU: 2 PID: 3257 Comm: syz-executor.3 Not tainted 5.10.0-syzkaller #0 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2~bpo12+1

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  9. CVE-2024-36007

    Élevée · CVSS 7.8EPSS 0,23%Correctif disponible

    mlxsw: spectrum_acl_tcam: Fix warning during rehash

    In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix warning during rehash As previously explained, the rehash delayed work migrates filters from one region to another. This is done by iterating over all chunks (all the filters with the same priority) in the region and in each chunk iterating over all the filters. When the work runs out of credits it stores the current chunk and entry as markers in the per-work context so that it would know where to resume the migration from the next time the work is scheduled. Upon error, the chunk marker is reset to NULL, but without resetting the entry marke

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  10. CVE-2024-36006

    Moyenne · CVSS 5.6EPSS 0,23%Correctif disponible

    mlxsw: spectrum_acl_tcam: Fix incorrect list API usage

    In the Linux kernel, the following vulnerability has been resolved: mlxsw: spectrum_acl_tcam: Fix incorrect list API usage Both the function that migrates all the chunks within a region and the function that migrates all the entries within a chunk call list_first_entry() on the respective lists without checking that the lists are not empty. This is incorrect usage of the API, which leads to the following warning [1]. Fix by returning if the lists are empty as there is nothing to migrate in this case. [1] WARNING: CPU: 0 PID: 6437 at drivers/net/ethernet/mellanox/mlxsw/spectrum_acl_tcam.c:1266 mlxsw_sp_acl_tcam_vchunk_migrate_all+0x1f1/0>

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  11. CVE-2024-36005

    Moyenne · CVSS 5.5EPSS 0,23%Correctif disponible

    netfilter: nf_tables: honor table dormant flag from netdev release event path

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: honor table dormant flag from netdev release event path Check for table dormant flag otherwise netdev release event path tries to unregister an already unregistered hook. [524854.857999] ------------[ cut here ]------------ [524854.858010] WARNING: CPU: 0 PID: 3386599 at net/netfilter/core.c:501 __nf_unregister_net_hook+0x21a/0x260 [...] [524854.858848] CPU: 0 PID: 3386599 Comm: kworker/u32:2 Not tainted 6.9.0-rc3+ #365 [524854.858869] Workqueue: netns cleanup_net [524854.858886] RIP: 0010:__nf_unregister_net_hook+0x21a/0x260 [524854.858903] Code: 24

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  12. CVE-2024-36004

    Moyenne · CVSS 5.7EPSS 0,25%Correctif disponible

    i40e: Do not use WQ_MEM_RECLAIM flag for workqueue

    In the Linux kernel, the following vulnerability has been resolved: i40e: Do not use WQ_MEM_RECLAIM flag for workqueue Issue reported by customer during SRIOV testing, call trace: When both i40e and the i40iw driver are loaded, a warning in check_flush_dependency is being triggered. This seems to be because of the i40e driver workqueue is allocated with the WQ_MEM_RECLAIM flag, and the i40iw one is not. Similar error was encountered on ice too and it was fixed by removing the flag. Do the same for i40e too. [Feb 9 09:08] ------------[ cut here ]------------ [ +0.000004] workqueue: WQ_MEM_RECLAIM i40e:i40e_service_task [i40e] is flushing

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  13. CVE-2024-35997

    Moyenne · CVSS 5.5EPSS 0,18%Correctif disponible

    HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up

    In the Linux kernel, the following vulnerability has been resolved: HID: i2c-hid: remove I2C_HID_READ_PENDING flag to prevent lock-up The flag I2C_HID_READ_PENDING is used to serialize I2C operations. However, this is not necessary, because I2C core already has its own locking for that. More importantly, this flag can cause a lock-up: if the flag is set in i2c_hid_xfer() and an interrupt happens, the interrupt handler (i2c_hid_irq) will check this flag and return immediately without doing anything, then the interrupt handler will be invoked again in an infinite loop. Since interrupt handler is an RT task, it takes over the CPU and the fla

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  14. CVE-2024-35990

    Élevée · CVSS 7.8EPSS 0,21%Correctif disponible

    dma: xilinx_dpdma: Fix locking

    In the Linux kernel, the following vulnerability has been resolved: dma: xilinx_dpdma: Fix locking There are several places where either chan->lock or chan->vchan.lock was not held. Add appropriate locking. This fixes lockdep warnings like [ 31.077578] ------------[ cut here ]------------ [ 31.077831] WARNING: CPU: 2 PID: 40 at drivers/dma/xilinx/xilinx_dpdma.c:834 xilinx_dpdma_chan_queue_transfer+0x274/0x5e0 [ 31.077953] Modules linked in: [ 31.078019] CPU: 2 PID: 40 Comm: kworker/u12:1 Not tainted 6.6.20+ #98 [ 31.078102] Hardware name: xlnx,zynqmp (DT) [ 31.078169] Workqueue: events_unbound deferred_probe_work_func [ 31.07

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  15. CVE-2024-35989

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    dmaengine: idxd: Fix oops during rmmod on single-CPU platforms

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix oops during rmmod on single-CPU platforms During the removal of the idxd driver, registered offline callback is invoked as part of the clean up process. However, on systems with only one CPU online, no valid target is available to migrate the perf context, resulting in a kernel oops: BUG: unable to handle page fault for address: 000000000002a2b8 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not-present page PGD 1470e1067 P4D 0 Oops: 0002 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 20 Comm: cpuhp/0 Not tainted 6.8.

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  16. CVE-2024-35988

    Moyenne · CVSS 5.7EPSS 0,21%Correctif disponible

    riscv: Fix TASK_SIZE on 64-bit NOMMU

    In the Linux kernel, the following vulnerability has been resolved: riscv: Fix TASK_SIZE on 64-bit NOMMU On NOMMU, userspace memory can come from anywhere in physical RAM. The current definition of TASK_SIZE is wrong if any RAM exists above 4G, causing spurious failures in the userspace access routines.

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  17. CVE-2024-35984

    Moyenne · CVSS 5.5EPSS 0,26%Correctif disponible

    i2c: smbus: fix NULL function pointer dereference

    In the Linux kernel, the following vulnerability has been resolved: i2c: smbus: fix NULL function pointer dereference Baruch reported an OOPS when using the designware controller as target only. Target-only modes break the assumption of one transfer function always being available. Fix this by always checking the pointer in __i2c_transfer. [wsa: dropped the simplification in core-smbus to avoid theoretical regressions]

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  18. CVE-2024-35982

    Moyenne · CVSS 5.1EPSS 0,26%Correctif disponible

    batman-adv: Avoid infinite loop trying to resize local TT

    In the Linux kernel, the following vulnerability has been resolved: batman-adv: Avoid infinite loop trying to resize local TT If the MTU of one of an attached interface becomes too small to transmit the local translation table then it must be resized to fit inside all fragments (when enabled) or a single packet. But if the MTU becomes too low to transmit even the header + the VLAN specific part then the resizing of the local TT will never succeed. This can for example happen when the usable space is 110 bytes and 11 VLANs are on top of batman-adv. In this case, at least 116 byte would be needed. There will just be an endless spam of ba

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  19. CVE-2024-35978

    Moyenne · CVSS 6.8EPSS 0,28%Correctif disponible

    Bluetooth: Fix memory leak in hci_req_sync_complete()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Fix memory leak in hci_req_sync_complete() In 'hci_req_sync_complete()', always free the previous sync request state before assigning reference to a new one.

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour
  20. CVE-2024-35976

    Élevée · CVSS 7.1EPSS 0,26%Correctif disponible

    xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING

    In the Linux kernel, the following vulnerability has been resolved: xsk: validate user input for XDP_{UMEM|COMPLETION}_FILL_RING syzbot reported an illegal copy in xsk_setsockopt() [1] Make sure to validate setsockopt() @optlen parameter. [1] 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 xsk_setsockopt+0x909/0xa40 net/xdp/xsk.c:1420 Read of size 4 at addr ffff888028c6cde3 by task syz-executor.0/7549 CPU: 0 PID: 7549 Comm: syz-executor.0 Not tainted 6.8.0-syzkaller-0

    • Mettez à jour vers 5.15.0-116.126~20.04.1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →