p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-nvidia-tegra-5.15 · Page n° 105

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

RSS ↗ JSON ↗
Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 2668

  1. CVE-2024-27034

    Élevée · CVSS 7.8EPSS 0,29%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  2. CVE-2024-27030

    Élevée · CVSS 7.8EPSS 0,23%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  3. CVE-2024-27028

    Moyenne · CVSS 6.5EPSS 1,18%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  4. CVE-2023-52650

    Moyenne · CVSS 5.5EPSS 0,3%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  5. CVE-2024-27024

    Élevée · CVSS 7.8EPSS 0,31%Correctif 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().

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  8. CVE-2024-27020

    Élevée · CVSS 7.8EPSS 0,22%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  9. CVE-2024-27019

    Élevée · CVSS 7.8EPSS 0,21%Correctif 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.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  10. CVE-2024-27017

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

    netfilter: nft_set_pipapo: walk over current view on netlink dump

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_pipapo: walk over current view on netlink dump The generation mask can be updated while netlink dump is in progress. The pipapo set backend walk iterator cannot rely on it to infer what view of the datastructure is to be used. Add notation to specify if user wants to read/update the set. Based on patch from Florian Westphal.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  11. CVE-2024-27016

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

    netfilter: flowtable: validate pppoe header

    In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: validate pppoe header Ensure there is sufficient room to access the protocol field of the PPPoe header. Validate it once before the flowtable lookup, then use a helper function to access protocol field.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  12. CVE-2024-27015

    Moyenne · CVSS 6.3EPSS 0,23%Correctif disponible

    netfilter: flowtable: incorrect pppoe tuple

    In the Linux kernel, the following vulnerability has been resolved: netfilter: flowtable: incorrect pppoe tuple pppoe traffic reaching ingress path does not match the flowtable entry because the pppoe header is expected to be at the network header offset. This bug causes a mismatch in the flow table lookup, so pppoe packets enter the classical forwarding path.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  13. CVE-2024-27013

    Moyenne · CVSS 5.5EPSS 0,27%Correctif disponible

    tun: limit printing rate when illegal packet received by tun dev

    In the Linux kernel, the following vulnerability has been resolved: tun: limit printing rate when illegal packet received by tun dev vhost_worker will call tun call backs to receive packets. If too many illegal packets arrives, tun_do_read will keep dumping packet contents. When console is enabled, it will costs much more cpu time to dump packet and soft lockup will be detected. net_ratelimit mechanism can be used to limit the dumping rate. PID: 33036 TASK: ffff949da6f20000 CPU: 23 COMMAND: "vhost-32980" #0 [fffffe00003fce50] crash_nmi_callback at ffffffff89249253 #1 [fffffe00003fce58] nmi_handle at ffffffff89225fa3 #2 [fffffe000

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  14. CVE-2024-27012

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

    netfilter: nf_tables: restore set elements when delete set fails

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: restore set elements when delete set fails From abort path, nft_mapelem_activate() needs to restore refcounters to the original state. Currently, it uses the set->ops->walk() to iterate over these set elements. The existing set iterator skips inactive elements in the next generation, this does not work from the abort path to restore the original state since it has to skip active elements instead (not inactive ones). This patch moves the check for inactive elements to the set iterator callback, then it reverses the logic for the .activate case which ne

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1030.30~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  15. CVE-2024-27009

    Moyenne · CVSS 4.7EPSS 0,18%Correctif disponible

    s390/cio: fix race condition during online processing

    In the Linux kernel, the following vulnerability has been resolved: s390/cio: fix race condition during online processing A race condition exists in ccw_device_set_online() that can cause the online process to fail, leaving the affected device in an inconsistent state. As a result, subsequent attempts to set that device online fail with return code ENODEV. The problem occurs when a path verification request arrives after a wait for final device state completed, but before the result state is evaluated. Fix this by ensuring that the CCW-device lock is held between determining final state and checking result state. Note that since: commit

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  16. CVE-2024-27008

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

    drm: nv04: Fix out of bounds access

    In the Linux kernel, the following vulnerability has been resolved: drm: nv04: Fix out of bounds access When Output Resource (dcb->or) value is assigned in fabricate_dcb_output(), there may be out of bounds access to dac_users array in case dcb->or is zero because ffs(dcb->or) is used as index there. The 'or' argument of fabricate_dcb_output() must be interpreted as a number of bit to set, not value. Utilize macros from 'enum nouveau_or' in calls instead of hardcoding. Found by Linux Verification Center (linuxtesting.org) with SVACE.

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  17. CVE-2024-27004

    Moyenne · CVSS 5.5EPSS 0,21%Correctif disponible

    clk: Get runtime PM before walking tree during disable_unused

    In the Linux kernel, the following vulnerability has been resolved: clk: Get runtime PM before walking tree during disable_unused Doug reported [1] the following hung task: INFO: task swapper/0:1 blocked for more than 122 seconds. Not tainted 5.15.149-21875-gf795ebc40eb8 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:swapper/0 state:D stack: 0 pid: 1 ppid: 0 flags:0x00000008 Call trace: __switch_to+0xf4/0x1f4 __schedule+0x418/0xb80 schedule+0x5c/0x10c rpm_resume+0xe0/0x52c rpm_resume+0x178/0x52c __pm_runtime_resume+0x58/0x98 clk_pm_runtime_get+0x30/0xb0 clk_disab

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  18. CVE-2024-27001

    Moyenne · CVSS 5.5EPSS 0,28%Correctif disponible

    comedi: vmk80xx: fix incomplete endpoint checking

    In the Linux kernel, the following vulnerability has been resolved: comedi: vmk80xx: fix incomplete endpoint checking While vmk80xx does have endpoint checking implemented, some things can fall through the cracks. Depending on the hardware model, URBs can have either bulk or interrupt type, and current version of vmk80xx_find_usb_endpoints() function does not take that fully into account. While this warning does not seem to be too harmful, at the very least it will crash systems with 'panic_on_warn' set on them. Fix the issue found by Syzkaller [1] by somewhat simplifying the endpoint checking process with usb_find_common_endpoints() and e

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  19. CVE-2024-27000

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

    serial: mxs-auart: add spinlock around changing cts state

    In the Linux kernel, the following vulnerability has been resolved: serial: mxs-auart: add spinlock around changing cts state The uart_handle_cts_change() function in serial_core expects the caller to hold uport->lock. For example, I have seen the below kernel splat, when the Bluetooth driver is loaded on an i.MX28 board. [ 85.119255] ------------[ cut here ]------------ [ 85.124413] WARNING: CPU: 0 PID: 27 at /drivers/tty/serial/serial_core.c:3453 uart_handle_cts_change+0xb4/0xec [ 85.134694] Modules linked in: hci_uart bluetooth ecdh_generic ecc wlcore_sdio configfs [ 85.143314] CPU: 0 PID: 27 Comm: kworker/u3:0 N

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

  20. CVE-2024-26999

    Moyenne · CVSS 5.5EPSS 0,18%Correctif disponible

    serial/pmac_zilog: Remove flawed mitigation for rx irq flood

    In the Linux kernel, the following vulnerability has been resolved: serial/pmac_zilog: Remove flawed mitigation for rx irq flood The mitigation was intended to stop the irq completely. That may be better than a hard lock-up but it turns out that you get a crash anyway if you're using pmac_zilog as a serial console: ttyPZ0: pmz: rx irq flood ! BUG: spinlock recursion on CPU#0, swapper/0 That's because the pr_err() call in pmz_receive_chars() results in pmz_console_write() attempting to lock a spinlock already locked in pmz_interrupt(). With CONFIG_DEBUG_SPINLOCK=y, this produces a fatal BUG splat. The spinlock in question is the one in str

    linux-nvidia-tegra-5.15Systèmes d’exploitation
    • Mettez à jour vers 5.15.0-1027.27~20.04.1
    Publication Mise à jour
    Avis original 1 ↗Avis original 2 ↗Avis original 3 ↗

Vérifiez votre serveur

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

Vérifiez votre serveur →