p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de linux-hwe-5.15 · Página 178

Vulnerabilidades publicadas para linux-hwe-5.15 en los últimos 30 días: 0. Incluidas en el catálogo KEV: 0.

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 4389

  1. CVE-2024-27053

    Alta · CVSS 8.8EPSS 1,65%Corrección disponible

    wifi: wilc1000: fix RCU usage in connect path

    In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: fix RCU usage in connect path With lockdep enabled, calls to the connect function from cfg802.11 layer lead to the following warning: ============================= WARNING: suspicious RCU usage 6.7.0-rc1-wt+ #333 Not tainted ----------------------------- drivers/net/wireless/microchip/wilc1000/hif.c:386 suspicious rcu_dereference_check() usage! [...] stack backtrace: CPU: 0 PID: 100 Comm: wpa_supplicant Not tainted 6.7.0-rc1-wt+ #333 Hardware name: Atmel SAMA5 unwind_backtrace from show_stack+0x18/0x1c show_stack from dump_stack_lvl+0x34/0x48 dump_stack_

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  2. CVE-2024-27052

    Alta · CVSS 7.8EPSS 0,3%Corrección disponible

    wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work

    In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work The workqueue might still be running, when the driver is stopped. To avoid a use-after-free, call cancel_work_sync() in rtl8xxxu_stop().

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  3. CVE-2024-27051

    Media · CVSS 5.5EPSS 0,27%Corrección disponible

    cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value

    In the Linux kernel, the following vulnerability has been resolved: cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return 0 in case of error. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  4. CVE-2024-27047

    Media · CVSS 5.5EPSS 0,28%Corrección disponible

    net: phy: fix phy_get_internal_delay accessing an empty array

    In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defining delay_values and rx-internal-delay-ps or tx-internal-delay-ps is defined to 0 in the device-tree. This will lead to "unable to handle kernel NULL pointer dereference at virtual address 0". To avoid this kernel oops, the test should be delay >= 0. As there is already delay < 0 test just before, the test could only be size == 0.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  5. CVE-2024-27046

    Media · CVSS 5.5EPSS 0,3%Corrección disponible

    nfp: flower: handle acti_netdevs allocation failure

    In the Linux kernel, the following vulnerability has been resolved: nfp: flower: handle acti_netdevs allocation failure The kmalloc_array() in nfp_fl_lag_do_work() will return null, if the physical memory has run out. As a result, if we dereference the acti_netdevs, the null pointer dereference bugs will happen. This patch adds a check to judge whether allocation failure occurs. If it happens, the delayed work will be rescheduled and try again.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  6. CVE-2024-27045

    Alta · CVSS 7EPSS 0,31%Corrección disponible

    drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()'

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()' Tell snprintf() to store at most 10 bytes in the output buffer instead of 30. Fixes the below: drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm_debugfs.c:1508 dp_dsc_clock_en_read() error: snprintf() is printing too much 30 vs 10

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  7. CVE-2024-27044

    Media · CVSS 5.5EPSS 0,28%Corrección disponible

    drm/amd/display: Fix potential NULL pointer dereferences in 'dcn10_set_output_transfer_func()'

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential NULL pointer dereferences in 'dcn10_set_output_transfer_func()' The 'stream' pointer is used in dcn10_set_output_transfer_func() before the check if 'stream' is NULL. Fixes the below: drivers/gpu/drm/amd/amdgpu/../display/dc/hwss/dcn10/dcn10_hwseq.c:1892 dcn10_set_output_transfer_func() warn: variable dereferenced before check 'stream' (see line 1875)

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  8. CVE-2024-27043

    Alta · CVSS 7.8EPSS 0,29%Corrección disponible

    media: edia: dvbdev: fix a use-after-free

    In the Linux kernel, the following vulnerability has been resolved: media: edia: dvbdev: fix a use-after-free In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed in several error-handling paths. However, *pdvbdev is not set to NULL after dvbdev's deallocation, causing use-after-frees in many places, for example, in the following call chain: budget_register |-> dvb_dmxdev_init |-> dvb_register_device |-> dvb_dmxdev_release |-> dvb_unregister_device |-> dvb_remove_device |-> dvb_device_put |-> kref_put When calling dvb_unregister_device, dmxd

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  9. CVE-2024-27039

    Media · CVSS 5.5EPSS 0,27%Corrección disponible

    clk: hisilicon: hi3559a: Fix an erroneous devm_kfree()

    In the Linux kernel, the following vulnerability has been resolved: clk: hisilicon: hi3559a: Fix an erroneous devm_kfree() 'p_clk' is an array allocated just before the for loop for all clk that need to be registered. It is incremented at each loop iteration. If a clk_register() call fails, 'p_clk' may point to something different from what should be freed. The best we can do, is to avoid this wrong release of memory.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  10. CVE-2024-27038

    Media · CVSS 5.5EPSS 0,29%Corrección disponible

    clk: Fix clk_core_get NULL dereference

    In the Linux kernel, the following vulnerability has been resolved: clk: Fix clk_core_get NULL dereference It is possible for clk_core_get to dereference a NULL in the following sequence: clk_core_get() of_clk_get_hw_from_clkspec() __of_clk_get_hw_from_provider() __clk_get_hw() __clk_get_hw() can return NULL which is dereferenced by clk_core_get() at hw->core. Prior to commit dde4eff47c82 ("clk: Look for parents with clkdev based clk_lookups") the check IS_ERR_OR_NULL() was performed which would have caught the NULL. Reading the description of this function it talks about returning NULL but that cannot be so at t

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  11. CVE-2024-27037

    Media · CVSS 5.5EPSS 0,27%Corrección disponible

    clk: zynq: Prevent null pointer dereference caused by kmalloc failure

    In the Linux kernel, the following vulnerability has been resolved: clk: zynq: Prevent null pointer dereference caused by kmalloc failure The kmalloc() in zynq_clk_setup() will return null if the physical memory has run out. As a result, if we use snprintf() to write data to the null address, the null pointer dereference bug will happen. This patch uses a stack variable to replace the kmalloc().

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  12. CVE-2024-27034

    Alta · CVSS 7.8EPSS 0,29%Corrección disponible

    f2fs: compress: fix to cover normal cluster write with cp_rwsem

    In the Linux kernel, the following vulnerability has been resolved: f2fs: compress: fix to cover normal cluster write with cp_rwsem When we overwrite compressed cluster w/ normal cluster, we should not unlock cp_rwsem during f2fs_write_raw_pages(), otherwise data will be corrupted if partial blocks were persisted before CP & SPOR, due to cluster metadata wasn't updated atomically.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  13. CVE-2024-27030

    Alta · CVSS 7.8EPSS 0,23%Corrección disponible

    octeontx2-af: Use separate handlers for interrupts

    In the Linux kernel, the following vulnerability has been resolved: octeontx2-af: Use separate handlers for interrupts For PF to AF interrupt vector and VF to AF vector same interrupt handler is registered which is causing race condition. When two interrupts are raised to two CPUs at same time then two cores serve same event corrupting the data.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  14. CVE-2024-27028

    Media · CVSS 6.5EPSS 1,18%Corrección disponible

    spi: spi-mt65xx: Fix NULL pointer access in interrupt handler

    In the Linux kernel, the following vulnerability has been resolved: spi: spi-mt65xx: Fix NULL pointer access in interrupt handler The TX buffer in spi_transfer can be a NULL pointer, so the interrupt handler may end up writing to the invalid memory and cause crashes. Add a check to trans->tx_buf before using it.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  15. CVE-2023-52650

    Media · CVSS 5.5EPSS 0,3%Corrección disponible

    drm/tegra: dsi: Add missing check for of_find_device_by_node

    In the Linux kernel, the following vulnerability has been resolved: drm/tegra: dsi: Add missing check for of_find_device_by_node Add check for the return value of of_find_device_by_node() and return the error if it fails in order to avoid NULL pointer dereference.

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  16. CVE-2024-27024

    Alta · CVSS 7.8EPSS 0,31%Corrección disponible

    net/rds: fix WARNING in rds_conn_connect_if_down

    In the Linux kernel, the following vulnerability has been resolved: net/rds: fix WARNING in rds_conn_connect_if_down If connection isn't established yet, get_mr() will fail, trigger connection after get_mr().

    • Actualiza a 5.15.0-113.123~20.04.1
    Publicación Actualización
  17. CVE-2024-27020

    Alta · CVSS 7.8EPSS 0,22%Corrección disponible

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

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_expr_type_get() nft_unregister_expr() can concurrent with __nft_expr_type_get(), and there is not any protection when iterate over nf_tables_expressions list in __nft_expr_type_get(). Therefore, there is potential data-race of nf_tables_expressions list entry. Use list_for_each_entry_rcu() to iterate over nf_tables_expressions list in __nft_expr_type_get(), and use rcu_read_lock() in the caller nft_expr_type_get() to protect the entire type query process.

    • Actualiza a 5.15.0-116.126~20.04.1
    Publicación Actualización
  18. CVE-2024-27019

    Alta · CVSS 7.8EPSS 0,21%Corrección disponible

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

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: Fix potential data-race in __nft_obj_type_get() nft_unregister_obj() can concurrent with __nft_obj_type_get(), and there is not any protection when iterate over nf_tables_objects list in __nft_obj_type_get(). Therefore, there is potential data-race of nf_tables_objects list entry. Use list_for_each_entry_rcu() to iterate over nf_tables_objects list in __nft_obj_type_get(), and use rcu_read_lock() in the caller nft_obj_type_get() to protect the entire type query process.

    • Actualiza a 5.15.0-116.126~20.04.1
    Publicación Actualización

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →