p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de linux-azure-4.15 · Página 23

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

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 1270

  1. CVE-2022-49388

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

    ubi: ubi_create_volume: Fix use-after-free when volume creation failed

    In the Linux kernel, the following vulnerability has been resolved: ubi: ubi_create_volume: Fix use-after-free when volume creation failed There is an use-after-free problem for 'eba_tbl' in ubi_create_volume()'s error handling path: ubi_eba_replace_table(vol, eba_tbl) vol->eba_tbl = tbl out_mapping: ubi_eba_destroy_table(eba_tbl) // Free 'eba_tbl' out_unlock: put_device(&vol->dev) vol_release kfree(tbl->entries) // UAF Fix it by removing redundant 'eba_tbl' releasing. Fetch a reproducer in [Link].

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  2. CVE-2022-49382

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

    soc: rockchip: Fix refcount leak in rockchip_grf_init

    In the Linux kernel, the following vulnerability has been resolved: soc: rockchip: Fix refcount leak in rockchip_grf_init of_find_matching_node_and_match returns a node pointer with refcount incremented, we should use of_node_put() on it when done. Add missing of_node_put() to avoid refcount leak.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  3. CVE-2022-49381

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

    jffs2: fix memory leak in jffs2_do_fill_super

    In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_do_fill_super If jffs2_iget() or d_make_root() in jffs2_do_fill_super() returns an error, we can observe the following kmemleak report: -------------------------------------------- unreferenced object 0xffff888105a65340 (size 64): comm "mount", pid 710, jiffies 4302851558 (age 58.239s) 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 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff859c45e5>] kmem_cache_alloc_trace+0x475/0x8a0 [<ffffffff86

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  4. CVE-2022-49375

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

    rtc: mt6397: check return value after calling platform_get_resource()

    In the Linux kernel, the following vulnerability has been resolved: rtc: mt6397: check return value after calling platform_get_resource() It will cause null-ptr-deref if platform_get_resource() returns NULL, we need check the return value.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  5. CVE-2022-49372

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

    tcp: tcp_rtx_synack() can be called from process context

    In the Linux kernel, the following vulnerability has been resolved: tcp: tcp_rtx_synack() can be called from process context Laurent reported the enclosed report [1] This bug triggers with following coditions: 0) Kernel built with CONFIG_DEBUG_PREEMPT=y 1) A new passive FastOpen TCP socket is created. This FO socket waits for an ACK coming from client to be a complete ESTABLISHED one. 2) A socket operation on this socket goes through lock_sock() release_sock() dance. 3) While the socket is owned by the user in step 2), a retransmit of the SYN is received and stored in socket backlog. 4) At release_sock() time, the socket back

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  6. CVE-2022-49370

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

    firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle

    In the Linux kernel, the following vulnerability has been resolved: firmware: dmi-sysfs: Fix memory leak in dmi_sysfs_register_handle kobject_init_and_add() takes reference even when it fails. According to the doc of kobject_init_and_add() If this function returns an error, kobject_put() must be called to properly clean up the memory associated with the object. Fix this issue by calling kobject_put().

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  7. CVE-2022-49368

    Alta · CVSS 7.1EPSS 0,28%Corrección disponible

    net: ethernet: mtk_eth_soc: out of bounds read in mtk_hwlro_get_fdir_entry()

    In the Linux kernel, the following vulnerability has been resolved: net: ethernet: mtk_eth_soc: out of bounds read in mtk_hwlro_get_fdir_entry() The "fsp->location" variable comes from user via ethtool_get_rxnfc(). Check that it is valid to prevent an out of bounds read.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  8. CVE-2022-49367

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

    net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register

    In the Linux kernel, the following vulnerability has been resolved: net: dsa: mv88e6xxx: Fix refcount leak in mv88e6xxx_mdios_register of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. mv88e6xxx_mdio_register() pass the device node to of_mdiobus_register(). We don't need the device node after it. Add missing of_node_put() to avoid refcount leak.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  9. CVE-2022-49354

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

    ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe

    In the Linux kernel, the following vulnerability has been resolved: ata: pata_octeon_cf: Fix refcount leak in octeon_cf_probe of_find_device_by_node() takes reference, we should use put_device() to release it when not need anymore. Add missing put_device() to avoid refcount leak.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  10. CVE-2022-49351

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

    net: altera: Fix refcount leak in altera_tse_mdio_create

    In the Linux kernel, the following vulnerability has been resolved: net: altera: Fix refcount leak in altera_tse_mdio_create Every iteration of for_each_child_of_node() decrements the reference count of the previous node. When break from a for_each_child_of_node() loop, we need to explicitly call of_node_put() on the child node when not need anymore. Add missing of_node_put() to avoid refcount leak.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  11. CVE-2022-49350

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

    net: mdio: unexport __init-annotated mdio_bus_init()

    In the Linux kernel, the following vulnerability has been resolved: net: mdio: unexport __init-annotated mdio_bus_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-tree c

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  12. CVE-2022-49349

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

    ext4: fix use-after-free in ext4_rename_dir_prepare

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix use-after-free in ext4_rename_dir_prepare We got issue as follows: EXT4-fs (loop0): mounted filesystem without journal. Opts: ,errors=continue ext4_get_first_dir_block: bh->b_data=0xffff88810bee6000 len=34478 ext4_get_first_dir_block: *parent_de=0xffff88810beee6ae bh->b_data=0xffff88810bee6000 ext4_rename_dir_prepare: [1] parent_de=0xffff88810beee6ae ================================================================== BUG: KASAN: use-after-free in ext4_rename_dir_prepare+0x152/0x220 Read of size 4 at addr ffff88810beee6ae by task rep/1895 CPU: 13 PID: 1895 Comm: re

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  13. CVE-2022-49347

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

    ext4: fix bug_on in ext4_writepages

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in ext4_writepages we got issue as follows: EXT4-fs error (device loop0): ext4_mb_generate_buddy:1141: group 0, block bitmap and bg descriptor inconsistent: 25 vs 31513 free cls ------------[ cut here ]------------ kernel BUG at fs/ext4/inode.c:2708! invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI CPU: 2 PID: 2147 Comm: rep Not tainted 5.18.0-rc2-next-20220413+ #155 RIP: 0010:ext4_writepages+0x1977/0x1c10 RSP: 0018:ffff88811d3e7880 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000001 RCX: ffff88811c098000 RDX: 0000000000000000 RSI: ffff88811c098000

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  14. CVE-2022-49345

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

    net: xfrm: unexport __init-annotated xfrm4_protocol_init()

    In the Linux kernel, the following vulnerability has been resolved: net: xfrm: unexport __init-annotated xfrm4_protocol_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the only in-

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  15. CVE-2022-49344

    Media · CVSS 4.7EPSS 0,19%Corrección disponible

    af_unix: Fix a data-race in unix_dgram_peer_wake_me().

    In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix a data-race in unix_dgram_peer_wake_me(). unix_dgram_poll() calls unix_dgram_peer_wake_me() without `other`'s lock held and check if its receive queue is full. Here we need to use unix_recvq_full_lockless() instead of unix_recvq_full(), otherwise KCSAN will report a data-race.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  16. CVE-2022-49343

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

    ext4: avoid cycles in directory h-tree

    In the Linux kernel, the following vulnerability has been resolved: ext4: avoid cycles in directory h-tree A maliciously corrupted filesystem can contain cycles in the h-tree stored inside a directory. That can easily lead to the kernel corrupting tree nodes that were already verified under its hands while doing a node split and consequently accessing unallocated memory. Fix the problem by verifying traversed block numbers are unique.

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  17. CVE-2022-49340

    Alta · CVSS 7.1EPSS 0,28%Corrección disponible

    ip_gre: test csum_start instead of transport header

    In the Linux kernel, the following vulnerability has been resolved: ip_gre: test csum_start instead of transport header GRE with TUNNEL_CSUM will apply local checksum offload on CHECKSUM_PARTIAL packets. ipgre_xmit must validate csum_start after an optional skb_pull, else lco_csum may trigger an overflow. The original check was if (csum && skb_checksum_start(skb) < skb->data) return -EINVAL; This had false positives when skb_checksum_start is undefined: when ip_summed is not CHECKSUM_PARTIAL. A discussed refinement was straightforward if (csum && skb->ip_summed == CHECKSUM_PARTIAL && skb_checksum_start(skb) < skb->data) retur

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  18. CVE-2022-49339

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

    net: ipv6: unexport __init-annotated seg6_hmac_init()

    In the Linux kernel, the following vulnerability has been resolved: net: ipv6: unexport __init-annotated seg6_hmac_init() EXPORT_SYMBOL and __init is a bad combination because the .init.text section is freed up after the initialization. Hence, modules cannot use symbols annotated __init. The access to a freed symbol may end up with kernel panic. modpost used to detect it, but it has been broken for a decade. Recently, I fixed modpost so it started to warn it again, then this showed up in linux-next builds. There are two ways to fix it: - Remove __init - Remove EXPORT_SYMBOL I chose the latter for this case because the caller (net/i

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  19. CVE-2022-49337

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

    ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: dlmfs: fix error handling of user_dlm_destroy_lock When user_dlm_destroy_lock failed, it didn't clean up the flags it set before exit. For USER_LOCK_IN_TEARDOWN, if this function fails because of lock is still in used, next time when unlink invokes this function, it will return succeed, and then unlink will remove inode and dentry if lock is not in used(file closed), but the dlm lock is still linked in dlm lock resource, then when bast come in, it will trigger a panic due to user-after-free. See the following panic call trace. To fix this, USER_LOCK_IN_TEARDOWN sh

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización
  20. CVE-2022-49335

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

    drm/amdgpu/cs: make commands with 0 chunks illegal behaviour.

    In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu/cs: make commands with 0 chunks illegal behaviour. Submitting a cs with 0 chunks, causes an oops later, found trying to execute the wrong userspace driver. MESA_LOADER_DRIVER_OVERRIDE=v3d glxinfo [172536.665184] BUG: kernel NULL pointer dereference, address: 00000000000001d8 [172536.665188] #PF: supervisor read access in kernel mode [172536.665189] #PF: error_code(0x0000) - not-present page [172536.665191] PGD 6712a0067 P4D 6712a0067 PUD 5af9ff067 PMD 0 [172536.665195] Oops: 0000 [#1] SMP NOPTI [172536.665197] CPU: 7 PID: 2769838 Comm: glxinfo Tainted: P

    • Actualiza a 4.15.0-1150.165
    Publicación Actualización

Comprueba tu servidor

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

Comprueba tu servidor →