p PatchFirst

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

Уязвимости linux-nvidia-tegra-5.15 · Страница 30

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

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

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

  1. CVE-2023-53489

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

    tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp.

    In the Linux kernel, the following vulnerability has been resolved: tcp/udp: Fix memleaks of sk and zerocopy skbs with TX timestamp. syzkaller reported [0] memory leaks of an UDP socket and ZEROCOPY skbs. We can reproduce the problem with these sequences: sk = socket(AF_INET, SOCK_DGRAM, 0) sk.setsockopt(SOL_SOCKET, SO_TIMESTAMPING, SOF_TIMESTAMPING_TX_SOFTWARE) sk.setsockopt(SOL_SOCKET, SO_ZEROCOPY, 1) sk.sendto(b'', MSG_ZEROCOPY, ('127.0.0.1', 53)) sk.close() sendmsg() calls msg_zerocopy_alloc(), which allocates a skb, sets skb->cb->ubuf.refcnt to 1, and calls sock_hold(). Here, struct ubuf_info_msgzc indirectly holds a refc

    • Обновитесь до 5.15.0-1016.16~20.04.1
  2. CVE-2023-53488

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

    IB/hfi1: Fix possible panic during hotplug remove

    In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix possible panic during hotplug remove During hotplug remove it is possible that the update counters work might be pending, and may run after memory has been freed. Cancel the update counters work before freeing memory.

    • Обновитесь до 5.15.0-1020.20~20.04.1
  3. CVE-2022-50468

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

    platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init()

    In the Linux kernel, the following vulnerability has been resolved: platform/chrome: cros_usbpd_notify: Fix error handling in cros_usbpd_notify_init() The following WARNING message was given when rmmod cros_usbpd_notify: Unexpected driver unregister! WARNING: CPU: 0 PID: 253 at drivers/base/driver.c:270 driver_unregister+0x8a/0xb0 Modules linked in: cros_usbpd_notify(-) CPU: 0 PID: 253 Comm: rmmod Not tainted 6.1.0-rc3 #24 ... Call Trace: <TASK> cros_usbpd_notify_exit+0x11/0x1e [cros_usbpd_notify] __x64_sys_delete_module+0x3c7/0x570 ? __ia32_sys_delete_module+0x570/0x570 ? lock_is_held_type+0xe3/0x140 ? syscall_enter_from

    • Обновитесь до 5.15.0-1014.14~20.04.1
  4. CVE-2022-50465

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

    ext4: fix leaking uninitialized memory in fast-commit journal

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix leaking uninitialized memory in fast-commit journal When space at the end of fast-commit journal blocks is unused, make sure to zero it out so that uninitialized memory is not leaked to disk.

    • Обновитесь до 5.15.0-1014.14~20.04.1
  5. CVE-2022-50463

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

    powerpc/52xx: Fix a resource leak in an error handling path

    In the Linux kernel, the following vulnerability has been resolved: powerpc/52xx: Fix a resource leak in an error handling path The error handling path of mpc52xx_lpbfifo_probe() has a request_irq() that is not balanced by a corresponding free_irq(). Add the missing call, as already done in the remove function.

    • Обновитесь до 5.15.0-1014.14~20.04.1
  6. CVE-2022-50462

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

    MIPS: vpe-mt: fix possible memory leak while module exiting

    In the Linux kernel, the following vulnerability has been resolved: MIPS: vpe-mt: fix possible memory leak while module exiting Afer commit 1fa5ae857bb1 ("driver core: get rid of struct device's bus_id string array"), the name of device is allocated dynamically, it need be freed when module exiting, call put_device() to give up reference, so that it can be freed in kobject_cleanup() when the refcount hit to 0. The vpe_device is static, so remove kfree() from vpe_device_release().

    • Обновитесь до 5.15.0-1014.14~20.04.1
  7. CVE-2022-50456

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

    btrfs: fix resolving backrefs for inline extent followed by prealloc

    In the Linux kernel, the following vulnerability has been resolved: btrfs: fix resolving backrefs for inline extent followed by prealloc If a file consists of an inline extent followed by a regular or prealloc extent, then a legitimate attempt to resolve a logical address in the non-inline region will result in add_all_parents reading the invalid offset field of the inline extent. If the inline extent item is placed in the leaf eb s.t. it is the first item, attempting to access the offset field will not only be meaningless, it will go past the end of the eb and cause this panic: [17.626048] BTRFS warning (device dm-2): bad eb member end:

    • Обновитесь до 5.15.0-1014.14~20.04.1
  8. CVE-2022-50453

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

    gpiolib: cdev: fix NULL-pointer dereferences

    In the Linux kernel, the following vulnerability has been resolved: gpiolib: cdev: fix NULL-pointer dereferences There are several places where we can crash the kernel by requesting lines, unbinding the GPIO device, then calling any of the system calls relevant to the GPIO character device's annonymous file descriptors: ioctl(), read(), poll(). While I observed it with the GPIO simulator, it will also happen for any of the GPIO devices that can be hot-unplugged - for instance any HID GPIO expander (e.g. CP2112). This affects both v1 and v2 uAPI. This fixes it partially by checking if gdev->chip is not NULL but it doesn't entirely remedy

    • Обновитесь до 5.15.0-1014.14~20.04.1
  9. CVE-2022-50451

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

    fs/ntfs3: Fix memory leak on ntfs_fill_super() error path

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Fix memory leak on ntfs_fill_super() error path syzbot reported kmemleak as below: BUG: memory leak unreferenced object 0xffff8880122f1540 (size 32): comm "a.out", pid 6664, jiffies 4294939771 (age 25.500s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 00 00 00 00 00 00 00 00 ed ff ed ff 00 00 00 00 ................ backtrace: [<ffffffff81b16052>] ntfs_init_fs_context+0x22/0x1c0 [<ffffffff8164aaa7>] alloc_fs_context+0x217/0x430 [<ffffffff81626dd4>] path_mount+0x704/0x1080 [<ffffffff8162

    • Обновитесь до 5.15.0-1014.14~20.04.1
    Опубликовано Обновлено
  10. CVE-2022-50449

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

    clk: samsung: Fix memory leak in _samsung_clk_register_pll()

    In the Linux kernel, the following vulnerability has been resolved: clk: samsung: Fix memory leak in _samsung_clk_register_pll() If clk_register() fails, @pll->rate_table may have allocated memory by kmemdup(), so it needs to be freed, otherwise will cause memory leak issue, this patch fixes it.

    • Обновитесь до 5.15.0-1014.14~20.04.1
  11. CVE-2023-53487

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

    powerpc/rtas_flash: allow user copy to flash block cache objects

    In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas_flash: allow user copy to flash block cache objects With hardened usercopy enabled (CONFIG_HARDENED_USERCOPY=y), using the /proc/powerpc/rtas/firmware_update interface to prepare a system firmware update yields a BUG(): kernel BUG at mm/usercopy.c:102! Oops: Exception in kernel mode, sig: 5 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries Modules linked in: CPU: 0 PID: 2232 Comm: dd Not tainted 6.5.0-rc3+ #2 Hardware name: IBM,8408-E8E POWER8E (raw) 0x4b0201 0xf000004 of:IBM,FW860.50 (SV860_146) hv:phyp pSeries NIP: c0000000005991d0

    • Обновитесь до 5.15.0-1020.20~20.04.1
  12. CVE-2023-53486

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

    fs/ntfs3: Enhance the attribute size check

    In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: Enhance the attribute size check This combines the overflow and boundary check so that all attribute size will be properly examined while enumerating them. [ 169.181521] BUG: KASAN: slab-out-of-bounds in run_unpack+0x2e3/0x570 [ 169.183161] Read of size 1 at addr ffff8880094b6240 by task mount/247 [ 169.184046] [ 169.184925] CPU: 0 PID: 247 Comm: mount Not tainted 6.0.0-rc7+ #3 [ 169.185908] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 169.187066] Call Trace: [ 169.187492] <TASK> [

    • Обновитесь до 5.15.0-1017.17~20.04.1
    Опубликовано Обновлено
  13. CVE-2023-53485

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

    fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev

    In the Linux kernel, the following vulnerability has been resolved: fs: jfs: Fix UBSAN: array-index-out-of-bounds in dbAllocDmapLev Syzkaller reported the following issue: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:1965:6 index -84 is out of range for type 's8[341]' (aka 'signed char[341]') CPU: 1 PID: 4995 Comm: syz-executor146 Not tainted 6.4.0-rc6-syzkaller-00037-gb6dad5178cea #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/27/2023 Call Trace: <TASK> __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x1e7/0x2d0 lib/dump_stack.c:106 ubsan_epilogue lib/ubsan.c:217 [inline] __ubsa

    • Обновитесь до 5.15.0-1019.19~20.04.1
    Опубликовано Обновлено
  14. CVE-2023-53484

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

    lib: cpu_rmap: Avoid use after free on rmap->obj array entries

    In the Linux kernel, the following vulnerability has been resolved: lib: cpu_rmap: Avoid use after free on rmap->obj array entries When calling irq_set_affinity_notifier() with NULL at the notify argument, it will cause freeing of the glue pointer in the corresponding array entry but will leave the pointer in the array. A subsequent call to free_irq_cpu_rmap() will try to free this entry again leading to possible use after free. Fix that by setting NULL to the array entry and checking that we have non-zero at the array entry when iterating over the array in free_irq_cpu_rmap(). The current code does not suffer from this since there are no

    • Обновитесь до 5.15.0-1017.17~20.04.1
    Опубликовано Обновлено
  15. CVE-2023-53482

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

    iommu: Fix error unwind in iommu_group_alloc()

    In the Linux kernel, the following vulnerability has been resolved: iommu: Fix error unwind in iommu_group_alloc() If either iommu_group_grate_file() fails then the iommu_group is leaked. Destroy it on these error paths. Found by kselftest/iommu/iommufd_fail_nth

    • Обновитесь до 5.15.0-1015.15~20.04.1
  16. CVE-2023-53481

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

    ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed

    In the Linux kernel, the following vulnerability has been resolved: ubi: ubi_wl_put_peb: Fix infinite loop when wear-leveling work failed Following process will trigger an infinite loop in ubi_wl_put_peb(): ubifs_bgt ubi_bgt ubifs_leb_unmap ubi_leb_unmap ubi_eba_unmap_leb ubi_wl_put_peb wear_leveling_worker e1 = rb_entry(rb_first(&ubi->used) e2 = get_peb_for_wl(ubi) ubi_io_read_vid_hdr // return err (flash fault) out_error: ubi->move_from = ubi->move_to = NULL wl_entry_destroy(ubi, e1) ubi->lookuptbl[e->pnum] = NULL retry: e = ubi->lookuptbl[pnum];

    • Обновитесь до 5.15.0-1016.16~20.04.1
    Опубликовано Обновлено
  17. CVE-2023-53480

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

    kobject: Add sanity check for kset->kobj.ktype in kset_register()

    In the Linux kernel, the following vulnerability has been resolved: kobject: Add sanity check for kset->kobj.ktype in kset_register() When I register a kset in the following way: static struct kset my_kset; kobject_set_name(&my_kset.kobj, "my_kset"); ret = kset_register(&my_kset); A null pointer dereference exception is occurred: [ 4453.568337] Unable to handle kernel NULL pointer dereference at \ virtual address 0000000000000028 ... ... [ 4453.810361] Call trace: [ 4453.813062] kobject_get_ownership+0xc/0x34 [ 4453.817493] kobject_add_internal+0x98/0x274 [ 4453.822005] kset_register+0x5c/0xb4 [ 4453.825820] my_kobj_init+0x44

    • Обновитесь до 5.15.0-1022.22~20.04.1
  18. CVE-2023-53477

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

    ipv6: Add lwtunnel encap size of all siblings in nexthop calculation

    In the Linux kernel, the following vulnerability has been resolved: ipv6: Add lwtunnel encap size of all siblings in nexthop calculation In function rt6_nlmsg_size(), the length of nexthop is calculated by multipling the nexthop length of fib6_info and the number of siblings. However if the fib6_info has no lwtunnel but the siblings have lwtunnels, the nexthop length is less than it should be, and it will trigger a warning in inet6_rt_notify() as follows: WARNING: CPU: 0 PID: 6082 at net/ipv6/route.c:6180 inet6_rt_notify+0x120/0x130 ...... Call Trace: <TASK> fib6_add_rt2node+0x685/0xa30 fib6_add+0x96/0x1b0 ip6_route_add+0x50/0xd0 inet

    • Обновитесь до 5.15.0-1016.16~20.04.1
  19. CVE-2023-53476

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

    iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry()

    In the Linux kernel, the following vulnerability has been resolved: iw_cxgb4: Fix potential NULL dereference in c4iw_fill_res_cm_id_entry() This condition needs to match the previous "if (epcp->state == LISTEN) {" exactly to avoid a NULL dereference of either "listen_ep" or "ep". The problem is that "epcp" has been re-assigned so just testing "if (epcp->state == LISTEN) {" a second time is not sufficient.

    • Обновитесь до 5.15.0-1015.15~20.04.1
  20. CVE-2023-53475

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

    usb: xhci: tegra: fix sleep in atomic call

    In the Linux kernel, the following vulnerability has been resolved: usb: xhci: tegra: fix sleep in atomic call When we set the dual-role port to Host mode, we observed the following splat: [ 167.057718] BUG: sleeping function called from invalid context at include/linux/sched/mm.h:229 [ 167.057872] Workqueue: events tegra_xusb_usb_phy_work [ 167.057954] Call trace: [ 167.057962] dump_backtrace+0x0/0x210 [ 167.057996] show_stack+0x30/0x50 [ 167.058020] dump_stack_lvl+0x64/0x84 [ 167.058065] dump_stack+0x14/0x34 [ 167.058100] __might_resched+0x144/0x180 [ 167.058140] __might_sleep+0x64/0xd0 [ 167.058171] slab_pre_alloc_hook.c

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

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

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

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