p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de linux-oracle-5.4 · Página 5

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

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 1758

  1. CVE-2022-50671

    Alta · CVSS 7.5EPSS 0,95%Corrección disponible

    RDMA/rxe: Fix "kernel NULL pointer dereference" error

    In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix "kernel NULL pointer dereference" error When rxe_queue_init in the function rxe_qp_init_req fails, both qp->req.task.func and qp->req.task.arg are not initialized. Because of creation of qp fails, the function rxe_create_qp will call rxe_qp_do_cleanup to handle allocated resource. Before calling __rxe_do_task, both qp->req.task.func and qp->req.task.arg should be checked.

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  2. CVE-2022-50670

    Sin evaluarEPSS 0,24%Corrección disponible

    mmc: omap_hsmmc: fix return value check of mmc_add_host()

    In the Linux kernel, the following vulnerability has been resolved: mmc: omap_hsmmc: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In the remove() path, mmc_remove_host() will be called to delete device, but it's not added yet, it will lead a kernel crash because of null-ptr-deref in device_del(). Fix this by checking the return value and goto error path wihch will call mmc_free_host().

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  3. CVE-2022-50669

    Sin evaluarEPSS 0,25%Corrección disponible

    misc: ocxl: fix possible name leak in ocxl_file_register_afu()

    In the Linux kernel, the following vulnerability has been resolved: misc: ocxl: fix possible name leak in ocxl_file_register_afu() If device_register() returns error in ocxl_file_register_afu(), the name allocated by dev_set_name() need be freed. As comment of device_register() says, it should use put_device() to give up the reference in the error path. So fix this by calling put_device(), then the name can be freed in kobject_cleanup(), and info is freed in info_release().

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  4. CVE-2022-50668

    Alta · CVSS 7.5EPSS 0,81%Corrección disponible

    ext4: fix deadlock due to mbcache entry corruption

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix deadlock due to mbcache entry corruption When manipulating xattr blocks, we can deadlock infinitely looping inside ext4_xattr_block_set() where we constantly keep finding xattr block for reuse in mbcache but we are unable to reuse it because its reference count is too big. This happens because cache entry for the xattr block is marked as reusable (e_reusable set) although its reference count is too big. When this inconsistency happens, this inconsistent state is kept indefinitely and so ext4_xattr_block_set() keeps retrying indefinitely. The inconsistent state is

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  5. CVE-2022-50659

    Sin evaluarEPSS 0,28%Corrección disponible

    hwrng: geode - Fix PCI device refcount leak

    In the Linux kernel, the following vulnerability has been resolved: hwrng: geode - Fix PCI device refcount leak for_each_pci_dev() is implemented by pci_get_device(). The comment of pci_get_device() says that it will increase the reference count for the returned pci_dev and also decrease the reference count for the input pci_dev @from if it is not NULL. If we break for_each_pci_dev() loop with pdev not NULL, we need to call pci_dev_put() to decrease the reference count. We add a new struct 'amd_geode_priv' to record pointer of the pci_dev and membase, and then add missing pci_dev_put() for the normal and error path.

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  6. CVE-2022-50656

    Alta · CVSS 8.1EPSS 0,34%Corrección disponible

    nfc: pn533: Clear nfc_target before being used

    In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Clear nfc_target before being used Fix a slab-out-of-bounds read that occurs in nla_put() called from nfc_genl_send_target() when target->sensb_res_len, which is duplicated from an nfc_target in pn533, is too large as the nfc_target is not properly initialized and retains garbage values. Clear nfc_targets with memset() before they are used. Found by a modified version of syzkaller. BUG: KASAN: slab-out-of-bounds in nla_put Call Trace: memcpy nla_put nfc_genl_dump_targets genl_lock_dumpit netlink_dump __netlink_dump_start genl_family_rcv_msg_dumpit genl

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  7. CVE-2022-50655

    Sin evaluarEPSS 0,21%Corrección disponible

    ppp: associate skb with a device at tx

    In the Linux kernel, the following vulnerability has been resolved: ppp: associate skb with a device at tx Syzkaller triggered flow dissector warning with the following: r0 = openat$ppp(0xffffffffffffff9c, &(0x7f0000000000), 0xc0802, 0x0) ioctl$PPPIOCNEWUNIT(r0, 0xc004743e, &(0x7f00000000c0)) ioctl$PPPIOCSACTIVE(r0, 0x40107446, &(0x7f0000000240)={0x2, &(0x7f0000000180)=[{0x20, 0x0, 0x0, 0xfffff034}, {0x6}]}) pwritev(r0, &(0x7f0000000040)=[{&(0x7f0000000140)='\x00!', 0x2}], 0x1, 0x0, 0x0) [ 9.485814] WARNING: CPU: 3 PID: 329 at net/core/flow_dissector.c:1016 __skb_flow_dissect+0x1ee0/0x1fa0 [ 9.485929] skb_get_poff+0x53/0xa0 [ 9.

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  8. CVE-2022-50653

    Sin evaluarEPSS 0,21%Corrección disponible

    mmc: atmel-mci: fix return value check of mmc_add_host()

    In the Linux kernel, the following vulnerability has been resolved: mmc: atmel-mci: fix return value check of mmc_add_host() mmc_add_host() may return error, if we ignore its return value, it will lead two issues: 1. The memory that allocated in mmc_alloc_host() is leaked. 2. In the remove() path, mmc_remove_host() will be called to delete device, but it's not added yet, it will lead a kernel crash because of null-ptr-deref in device_del(). So fix this by checking the return value and calling mmc_free_host() in the error path.

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  9. CVE-2022-50652

    Sin evaluarEPSS 0,23%Corrección disponible

    uio: uio_dmem_genirq: Fix missing unlock in irq configuration

    In the Linux kernel, the following vulnerability has been resolved: uio: uio_dmem_genirq: Fix missing unlock in irq configuration Commit b74351287d4b ("uio: fix a sleep-in-atomic-context bug in uio_dmem_genirq_irqcontrol()") started calling disable_irq() without holding the spinlock because it can sleep. However, that fix introduced another bug: if interrupt is already disabled and a new disable request comes in, then the spinlock is not unlocked: root@localhost:~# printf '\x00\x00\x00\x00' > /dev/uio0 root@localhost:~# printf '\x00\x00\x00\x00' > /dev/uio0 root@localhost:~# [ 14.851538] BUG: scheduling while atomic: bash/223/0x00000002

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  10. CVE-2022-50649

    Sin evaluarEPSS 0,21%Corrección disponible

    power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type()

    In the Linux kernel, the following vulnerability has been resolved: power: supply: adp5061: fix out-of-bounds read in adp5061_get_chg_type() ADP5061_CHG_STATUS_1_CHG_STATUS is masked with 0x07, which means a length of 8, but adp5061_chg_type array size is 4, may end up reading 4 elements beyond the end of the adp5061_chg_type[] array.

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  11. CVE-2022-50647

    Sin evaluarEPSS 0,21%Corrección disponible

    RISC-V: Make port I/O string accessors actually work

    In the Linux kernel, the following vulnerability has been resolved: RISC-V: Make port I/O string accessors actually work Fix port I/O string accessors such as `insb', `outsb', etc. which use the physical PCI port I/O address rather than the corresponding memory mapping to get at the requested location, which in turn breaks at least accesses made by our parport driver to a PCIe parallel port such as: PCI parallel port detected: 1415:c118, I/O at 0x1000(0x1008), IRQ 20 parport0: PC-style at 0x1000 (0x1008), irq 20, using FIFO [PCSPP,TRISTATE,COMPAT,EPP,ECP] causing a memory access fault: Unable to handle kernel access to user memory withou

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  12. CVE-2022-50646

    Sin evaluarEPSS 0,21%Corrección disponible

    scsi: hpsa: Fix possible memory leak in hpsa_init_one()

    In the Linux kernel, the following vulnerability has been resolved: scsi: hpsa: Fix possible memory leak in hpsa_init_one() The hpda_alloc_ctlr_info() allocates h and its field reply_map. However, in hpsa_init_one(), if alloc_percpu() failed, the hpsa_init_one() jumps to clean1 directly, which frees h and leaks the h->reply_map. Fix by calling hpda_free_ctlr_info() to release h->replay_map and h instead free h directly.

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  13. CVE-2022-50645

    Sin evaluarEPSS 0,21%Corrección disponible

    EDAC/i10nm: fix refcount leak in pci_get_dev_wrapper()

    In the Linux kernel, the following vulnerability has been resolved: EDAC/i10nm: fix refcount leak in pci_get_dev_wrapper() As the comment of pci_get_domain_bus_and_slot() says, it returns a PCI device with refcount incremented, so it doesn't need to call an extra pci_dev_get() in pci_get_dev_wrapper(), and the PCI device needs to be put in the error path.

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  14. CVE-2022-50644

    Sin evaluarEPSS 0,24%Corrección disponible

    clk: ti: dra7-atl: Fix reference leak in of_dra7_atl_clk_probe

    In the Linux kernel, the following vulnerability has been resolved: clk: ti: dra7-atl: Fix reference leak in of_dra7_atl_clk_probe pm_runtime_get_sync() will increment pm usage counter. Forgetting to putting operation will result in reference leak. Add missing pm_runtime_put_sync in some error paths.

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  15. CVE-2022-50641

    Sin evaluarEPSS 0,24%Corrección disponible

    HSI: omap_ssi: Fix refcount leak in ssi_probe

    In the Linux kernel, the following vulnerability has been resolved: HSI: omap_ssi: Fix refcount leak in ssi_probe When returning or breaking early from a for_each_available_child_of_node() loop, we need to explicitly call of_node_put() on the child node to possibly release the node.

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  16. CVE-2022-50640

    Sin evaluarEPSS 0,21%Corrección disponible

    mmc: core: Fix kernel panic when remove non-standard SDIO card

    In the Linux kernel, the following vulnerability has been resolved: mmc: core: Fix kernel panic when remove non-standard SDIO card SDIO tuple is only allocated for standard SDIO card, especially it causes memory corruption issues when the non-standard SDIO card has removed, which is because the card device's reference counter does not increase for it at sdio_init_func(), but all SDIO card device reference counter gets decreased at sdio_release_func().

    • Actualiza a 5.4.0-1093.102~18.04.1
    Publicación Actualización
  17. CVE-2022-50638

    Sin evaluarEPSS 0,24%Corrección disponible

    ext4: fix bug_on in __es_tree_search caused by bad boot loader inode

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on in __es_tree_search caused by bad boot loader inode We got a issue as fllows: ================================================================== kernel BUG at fs/ext4/extents_status.c:203! invalid opcode: 0000 [#1] PREEMPT SMP CPU: 1 PID: 945 Comm: cat Not tainted 6.0.0-next-20221007-dirty #349 RIP: 0010:ext4_es_end.isra.0+0x34/0x42 RSP: 0018:ffffc9000143b768 EFLAGS: 00010203 RAX: 0000000000000000 RBX: ffff8881769cd0b8 RCX: 0000000000000000 RDX: 0000000000000000 RSI: ffffffff8fc27cf7 RDI: 00000000ffffffff RBP: ffff8881769cd0bc R08: 0000000000000000

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  18. CVE-2022-50636

    Sin evaluarEPSS 0,21%Corrección disponible

    PCI: Fix pci_device_is_present() for VFs by checking PF

    In the Linux kernel, the following vulnerability has been resolved: PCI: Fix pci_device_is_present() for VFs by checking PF pci_device_is_present() previously didn't work for VFs because it reads the Vendor and Device ID, which are 0xffff for VFs, which looks like they aren't present. Check the PF instead. Wei Gong reported that if virtio I/O is in progress when the driver is unbound or "0" is written to /sys/.../sriov_numvfs, the virtio I/O operation hangs, which may result in output like this: task:bash state:D stack: 0 pid: 1773 ppid: 1241 flags:0x00004002 Call Trace: schedule+0x4f/0xc0 blk_mq_freeze_queue_wait+0x69/0xa0

    • Actualiza a 5.4.0-1094.103~18.04.1
    Publicación Actualización
  19. CVE-2022-50626

    Sin evaluarEPSS 0,23%Corrección disponible

    media: dvb-usb: fix memory leak in dvb_usb_adapter_init()

    In the Linux kernel, the following vulnerability has been resolved: media: dvb-usb: fix memory leak in dvb_usb_adapter_init() Syzbot reports a memory leak in "dvb_usb_adapter_init()". The leak is due to not accounting for and freeing current iteration's adapter->priv in case of an error. Currently if an error occurs, it will exit before incrementing "num_adapters_initalized", which is used as a reference counter to free all adap->priv in "dvb_usb_adapter_exit()". There are multiple error paths that can exit from before incrementing the counter. Including the error handling paths for "dvb_usb_adapter_stream_init()", "dvb_usb_adapter_dvb_init

    • Actualiza a 5.4.0-1094.103~18.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 →