p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de linux-oracle-5.15 · Page n° 34

Vulnérabilité publiée pour linux-oracle-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 : 4250

  1. CVE-2023-53513

    Moyenne · CVSS 5.5EPSS 0,15%Correctif disponible

    nbd: fix incomplete validation of ioctl arg

    In the Linux kernel, the following vulnerability has been resolved: nbd: fix incomplete validation of ioctl arg We tested and found an alarm caused by nbd_ioctl arg without verification. The UBSAN warning calltrace like below: UBSAN: Undefined behaviour in fs/buffer.c:1709:35 signed integer overflow: -9223372036854775808 - 1 cannot be represented in type 'long long int' CPU: 3 PID: 2523 Comm: syz-executor.0 Not tainted 4.19.90 #1 Hardware name: linux,dummy-virt (DT) Call trace: dump_backtrace+0x0/0x3f0 arch/arm64/kernel/time.c:78 show_stack+0x28/0x38 arch/arm64/kernel/traps.c:158 __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x1

    • Mettez à jour vers 5.15.0-1042.48~20.04.1
    Publication Mise à jour
  2. CVE-2023-53506

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

    udf: Do not bother merging very long extents

    In the Linux kernel, the following vulnerability has been resolved: udf: Do not bother merging very long extents When merging very long extents we try to push as much length as possible to the first extent. However this is unnecessarily complicated and not really worth the trouble. Furthermore there was a bug in the logic resulting in corrupting extents in the file as syzbot reproducer shows. So just don't bother with the merging of extents that are too long together.

    • Mettez à jour vers 5.15.0-1037.43~20.04.1
    Publication Mise à jour
  3. CVE-2023-53505

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    clk: tegra: tegra124-emc: Fix potential memory leak

    In the Linux kernel, the following vulnerability has been resolved: clk: tegra: tegra124-emc: Fix potential memory leak The tegra and tegra needs to be freed in the error handling path, otherwise it will be leaked.

    • Mettez à jour vers 5.15.0-1045.51~20.04.1
    Publication Mise à jour
  4. CVE-2023-53503

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

    ext4: allow ext4_get_group_info() to fail

    In the Linux kernel, the following vulnerability has been resolved: ext4: allow ext4_get_group_info() to fail Previously, ext4_get_group_info() would treat an invalid group number as BUG(), since in theory it should never happen. However, if a malicious attaker (or fuzzer) modifies the superblock via the block device while it is the file system is mounted, it is possible for s_first_data_block to get set to a very large number. In that case, when calculating the block group of some block number (such as the starting block of a preallocation region), could result in an underflow and very large block group number. Then the BUG_ON check in

    • Mettez à jour vers 5.15.0-1042.48~20.04.1
    Publication Mise à jour
  5. CVE-2023-53501

    Moyenne · CVSS 6.7EPSS 0,15%Correctif disponible

    iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind

    In the Linux kernel, the following vulnerability has been resolved: iommu/amd/iommu_v2: Fix pasid_state refcount dec hit 0 warning on pasid unbind When unbinding pasid - a race condition exists vs outstanding page faults. To prevent this, the pasid_state object contains a refcount. * set to 1 on pasid bind * incremented on each ppr notification start * decremented on each ppr notification done * decremented on pasid unbind Since refcount_dec assumes that refcount will never reach 0: the current implementation causes the following to be invoked on pasid unbind: REFCOUNT_WARN("decrement hit 0; leaking memory") F

    • Mettez à jour vers 5.15.0-1051.57~20.04.1
    Publication Mise à jour
  6. CVE-2023-53500

    Élevée · CVSS 7.3EPSS 0,16%Correctif disponible

    xfrm: fix slab-use-after-free in decode_session6

    In the Linux kernel, the following vulnerability has been resolved: xfrm: fix slab-use-after-free in decode_session6 When the xfrm device is set to the qdisc of the sfb type, the cb field of the sent skb may be modified during enqueuing. Then, slab-use-after-free may occur when the xfrm device sends IPv6 packets. The stack information is as follows: BUG: KASAN: slab-use-after-free in decode_session6+0x103f/0x1890 Read of size 1 at addr ffff8881111458ef by task swapper/3/0 CPU: 3 PID: 0 Comm: swapper/3 Not tainted 6.4.0-next-20230707 #409 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-1.fc33 04/01/2014 Call Trace: <IRQ>

    • Mettez à jour vers 5.15.0-1049.55~20.04.1
    Publication Mise à jour
  7. CVE-2023-53499

    Élevée · CVSS 7EPSS 0,16%Correctif disponible

    virtio_net: Fix error unwinding of XDP initialization

    In the Linux kernel, the following vulnerability has been resolved: virtio_net: Fix error unwinding of XDP initialization When initializing XDP in virtnet_open(), some rq xdp initialization may hit an error causing net device open failed. However, previous rqs have already initialized XDP and enabled NAPI, which is not the expected behavior. Need to roll back the previous rq initialization to avoid leaks in error unwinding of init code. Also extract helper functions of disable and enable queue pairs. Use newly introduced disable helper function in error unwinding and virtnet_close. Use enable helper function in virtnet_open.

    • Mettez à jour vers 5.15.0-1042.48~20.04.1
    Publication Mise à jour
  8. CVE-2023-53498

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    drm/amd/display: Fix potential null dereference

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix potential null dereference The adev->dm.dc pointer can be NULL and dereferenced in amdgpu_dm_fini() without checking. Add a NULL pointer check before calling dc_dmub_srv_destroy(). Found by Linux Verification Center (linuxtesting.org) with SVACE.

    • Mettez à jour vers 5.15.0-1040.46~20.04.1
    Publication Mise à jour
  9. CVE-2023-53495

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

    net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc()

    In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mvpp2_main: fix possible OOB write in mvpp2_ethtool_get_rxnfc() rules is allocated in ethtool_get_rxnfc and the size is determined by rule_cnt from user space. So rule_cnt needs to be check before using rules to avoid OOB writing or NULL pointer dereference.

    • Mettez à jour vers 5.15.0-1051.57~20.04.1
    Publication Mise à jour
  10. CVE-2023-53494

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

    crypto: xts - Handle EBUSY correctly

    In the Linux kernel, the following vulnerability has been resolved: crypto: xts - Handle EBUSY correctly As it is xts only handles the special return value of EINPROGRESS, which means that in all other cases it will free data related to the request. However, as the caller of xts may specify MAY_BACKLOG, we also need to expect EBUSY and treat it in the same way. Otherwise backlogged requests will trigger a use-after-free.

    • Mettez à jour vers 5.15.0-1037.43~20.04.1
    Publication Mise à jour
  11. CVE-2023-53492

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

    netfilter: nf_tables: do not ignore genmask when looking up chain by id

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not ignore genmask when looking up chain by id When adding a rule to a chain referring to its ID, if that chain had been deleted on the same batch, the rule might end up referring to a deleted chain. This will lead to a WARNING like following: [ 33.098431] ------------[ cut here ]------------ [ 33.098678] WARNING: CPU: 5 PID: 69 at net/netfilter/nf_tables_api.c:2037 nf_tables_chain_destroy+0x23d/0x260 [ 33.099217] Modules linked in: [ 33.099388] CPU: 5 PID: 69 Comm: kworker/5:1 Not tainted 6.4.0+ #409 [ 33.099726] Workqueue: events nf_ta

    • Mettez à jour vers 5.15.0-1039.45~20.04.1
    Publication Mise à jour
  12. CVE-2023-53489

    Moyenne · CVSS 6.8EPSS 0,16%Correctif disponible

    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

    • Mettez à jour vers 5.15.0-1040.46~20.04.1
    Publication Mise à jour
  13. CVE-2023-53488

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    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.

    • Mettez à jour vers 5.15.0-1049.55~20.04.1
    Publication Mise à jour
  14. CVE-2022-50469

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    staging: rtl8723bs: fix potential memory leak in rtw_init_drv_sw()

    In the Linux kernel, the following vulnerability has been resolved: staging: rtl8723bs: fix potential memory leak in rtw_init_drv_sw() In rtw_init_drv_sw(), there are various init functions are called to populate the padapter structure and some checks for their return value. However, except for the first one error path, the other five error paths do not properly release the previous allocated resources, which leads to various memory leaks. This patch fixes them and keeps the success and error separate. Note that these changes keep the form of `rtw_init_drv_sw()` in "drivers/staging/r8188eu/os_dep/os_intfs.c". As there is no proper device t

    • Mettez à jour vers 5.15.0-1029.35~20.04.1
    Publication Mise à jour
  15. CVE-2022-50468

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    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

    • Mettez à jour vers 5.15.0-1032.38~20.04.1
    Publication Mise à jour
  16. CVE-2022-50466

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    fs/binfmt_elf: Fix memory leak in load_elf_binary()

    In the Linux kernel, the following vulnerability has been resolved: fs/binfmt_elf: Fix memory leak in load_elf_binary() There is a memory leak reported by kmemleak: unreferenced object 0xffff88817104ef80 (size 224): comm "xfs_admin", pid 47165, jiffies 4298708825 (age 1333.476s) hex dump (first 32 bytes): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................ 60 a8 b3 00 81 88 ff ff a8 10 5a 00 81 88 ff ff `.........Z..... backtrace: [<ffffffff819171e1>] __alloc_file+0x21/0x250 [<ffffffff81918061>] alloc_empty_file+0x41/0xf0 [<ffffffff81948cda>] path_openat+0xea/0x3d30 [<fffffff

    • Mettez à jour vers 5.15.0-1029.35~20.04.1
    Publication Mise à jour
  17. CVE-2022-50465

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    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.

    • Mettez à jour vers 5.15.0-1032.38~20.04.1
    Publication Mise à jour
  18. CVE-2022-50463

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    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.

    • Mettez à jour vers 5.15.0-1032.38~20.04.1
    Publication Mise à jour
  19. CVE-2022-50462

    Moyenne · CVSS 5.5EPSS 0,16%Correctif disponible

    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().

    • Mettez à jour vers 5.15.0-1032.38~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 →