p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de linux-fips · Página 189

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

Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 5102

  1. CVE-2024-43900

    Alta · CVSS 7.8EPSS 0,21%Sin corrección publicada

    media: xc2028: avoid use-after-free in load_firmware_cb()

    In the Linux kernel, the following vulnerability has been resolved: media: xc2028: avoid use-after-free in load_firmware_cb() syzkaller reported use-after-free in load_firmware_cb() [1]. The reason is because the module allocated a struct tuner in tuner_probe(), and then the module initialization failed, the struct tuner was released. A worker which created during module initialization accesses this struct tuner later, it caused use-after-free. The process is as follows: task-6504 worker_thread tuner_probe <= alloc dvb_frontend [2] ... request_firmware_nowait <= create a worker ... tun

    Publicación Actualización
  2. CVE-2024-43893

    Media · CVSS 5.5EPSS 0,26%Sin corrección publicada

    serial: core: check uartclk for zero to avoid divide by zero

    In the Linux kernel, the following vulnerability has been resolved: serial: core: check uartclk for zero to avoid divide by zero Calling ioctl TIOCSSERIAL with an invalid baud_base can result in uartclk being zero, which will result in a divide by zero error in uart_get_divisor(). The check for uartclk being zero in uart_set_info() needs to be done before other settings are made as subsequent calls to ioctl TIOCSSERIAL for the same port would be impacted if the uartclk check was done where uartclk gets set. Oops: divide error: 0000 PREEMPT SMP KASAN PTI RIP: 0010:uart_get_divisor (drivers/tty/serial/serial_core.c:580) Call Trace: <TASK>

    Publicación Actualización
  3. CVE-2024-43892

    Alta · CVSS 7.8EPSS 0,25%Sin corrección publicada

    memcg: protect concurrent access to mem_cgroup_idr

    In the Linux kernel, the following vulnerability has been resolved: memcg: protect concurrent access to mem_cgroup_idr Commit 73f576c04b94 ("mm: memcontrol: fix cgroup creation failure after many small jobs") decoupled the memcg IDs from the CSS ID space to fix the cgroup creation failures. It introduced IDR to maintain the memcg ID space. The IDR depends on external synchronization mechanisms for modifications. For the mem_cgroup_idr, the idr_alloc() and idr_replace() happen within css callback and thus are protected through cgroup_mutex from concurrent modifications. However idr_remove() for mem_cgroup_idr was not protected against co

    Publicación Actualización
  4. CVE-2024-43884

    Media · CVSS 5.5EPSS 0,26%Sin corrección publicada

    Bluetooth: MGMT: Add error handling to pair_device()

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: MGMT: Add error handling to pair_device() hci_conn_params_add() never checks for a NULL value and could lead to a NULL pointer dereference causing a crash. Fixed by adding error handling in the function.

    Publicación Actualización
  5. CVE-2024-43883

    Crítica · CVSS 9.8EPSS 0,65%Sin corrección publicada

    usb: vhci-hcd: Do not drop references before new references are gained

    In the Linux kernel, the following vulnerability has been resolved: usb: vhci-hcd: Do not drop references before new references are gained At a few places the driver carries stale pointers to references that can still be used. Make sure that does not happen. This strictly speaking closes ZDI-CAN-22273, though there may be similar races in the driver.

    Publicación Actualización
  6. CVE-2022-48938

    Media · CVSS 5.5EPSS 0,21%Sin corrección publicada

    CDC-NCM: avoid overflow in sanity checking

    In the Linux kernel, the following vulnerability has been resolved: CDC-NCM: avoid overflow in sanity checking A broken device may give an extreme offset like 0xFFF0 and a reasonable length for a fragment. In the sanity check as formulated now, this will create an integer overflow, defeating the sanity check. Both offset and offset + len need to be checked in such a manner that no overflow can occur. And those quantities should be unsigned.

    Publicación Actualización
  7. CVE-2022-48931

    Media · CVSS 4.7EPSS 0,17%Sin corrección publicada

    configfs: fix a race in configfs_{,un}register_subsystem()

    In the Linux kernel, the following vulnerability has been resolved: configfs: fix a race in configfs_{,un}register_subsystem() When configfs_register_subsystem() or configfs_unregister_subsystem() is executing link_group() or unlink_group(), it is possible that two processes add or delete list concurrently. Some unfortunate interleavings of them can cause kernel panic. One of cases is: A --> B --> C --> D A <-- B <-- C <-- D delete list_head *B | delete list_head *C --------------------------------|----------------------------------- configfs_unregister_subsystem | configfs_unregister_subsystem unlink_group

    Publicación Actualización
  8. CVE-2022-48930

    Media · CVSS 5.5EPSS 0,17%Sin corrección publicada

    RDMA/ib_srp: Fix a deadlock

    In the Linux kernel, the following vulnerability has been resolved: RDMA/ib_srp: Fix a deadlock Remove the flush_workqueue(system_long_wq) call since flushing system_long_wq is deadlock-prone and since that call is redundant with a preceding cancel_work_sync()

    Publicación Actualización
  9. CVE-2022-48928

    Media · CVSS 5.5EPSS 0,21%Sin corrección publicada

    iio: adc: men_z188_adc: Fix a resource leak in an error handling path

    In the Linux kernel, the following vulnerability has been resolved: iio: adc: men_z188_adc: Fix a resource leak in an error handling path If iio_device_register() fails, a previous ioremap() is left unbalanced. Update the error handling path and add the missing iounmap() call, as already done in the remove function.

    Publicación Actualización
  10. CVE-2022-48943

    Alta · CVSS 7.1EPSS 0,25%Sin corrección publicada

    KVM: x86/mmu: make apf token non-zero to fix bug

    In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: make apf token non-zero to fix bug In current async pagefault logic, when a page is ready, KVM relies on kvm_arch_can_dequeue_async_page_present() to determine whether to deliver a READY event to the Guest. This function test token value of struct kvm_vcpu_pv_apf_data, which must be reset to zero by Guest kernel when a READY event is finished by Guest. If value is zero meaning that a READY event is done, so the KVM can deliver another. But the kvm_arch_setup_async_pf() may produce a valid token with zero value, which is confused with previous mention and may l

    Publicación Actualización
  11. CVE-2022-48911

    Alta · CVSS 7.8EPSS 0,21%Sin corrección publicada

    netfilter: nf_queue: fix possible use-after-free

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_queue: fix possible use-after-free Eric Dumazet says: The sock_hold() side seems suspect, because there is no guarantee that sk_refcnt is not already 0. On failure, we cannot queue the packet and need to indicate an error. The packet will be dropped by the caller. v2: split skb prefetch hunk into separate change

    Publicación Actualización
  12. CVE-2022-48910

    Media · CVSS 6.8EPSS 0,21%Sin corrección publicada

    net: ipv6: ensure we call ipv6_mc_down() at most once

    In the Linux kernel, the following vulnerability has been resolved: net: ipv6: ensure we call ipv6_mc_down() at most once There are two reasons for addrconf_notify() to be called with NETDEV_DOWN: either the network device is actually going down, or IPv6 was disabled on the interface. If either of them stays down while the other is toggled, we repeatedly call the code for NETDEV_DOWN, including ipv6_mc_down(), while never calling the corresponding ipv6_mc_up() in between. This will cause a new entry in idev->mc_tomb to be allocated for each multicast group the interface is subscribed to, which in turn leaks one struct ifmcaddr6 per nontriv

    Publicación Actualización
  13. CVE-2022-48908

    Media · CVSS 5.5EPSS 0,21%Sin corrección publicada

    net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()

    In the Linux kernel, the following vulnerability has been resolved: net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe() During driver initialization, the pointer of card info, i.e. the variable 'ci' is required. However, the definition of 'com20020pci_id_table' reveals that this field is empty for some devices, which will cause null pointer dereference when initializing these devices. The following log reveals it: [ 3.973806] KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] [ 3.973819] RIP: 0010:com20020pci_probe+0x18d/0x13e0 [com20020_pci] [ 3.975181] Call Trace: [ 3.976208] local_pci_probe

    Publicación Actualización
  14. CVE-2022-48901

    Alta · CVSS 7.1EPSS 0,21%Sin corrección publicada

    btrfs: do not start relocation until in progress drops are done

    In the Linux kernel, the following vulnerability has been resolved: btrfs: do not start relocation until in progress drops are done We hit a bug with a recovering relocation on mount for one of our file systems in production. I reproduced this locally by injecting errors into snapshot delete with balance running at the same time. This presented as an error while looking up an extent item WARNING: CPU: 5 PID: 1501 at fs/btrfs/extent-tree.c:866 lookup_inline_extent_backref+0x647/0x680 CPU: 5 PID: 1501 Comm: btrfs-balance Not tainted 5.16.0-rc8+ #8 RIP: 0010:lookup_inline_extent_backref+0x647/0x680 RSP: 0018:ffffae0a023ab960 EFLAGS:

    Publicación Actualización
  15. CVE-2023-52907

    Alta · CVSS 7.8EPSS 0,24%Sin corrección publicada

    nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame()

    In the Linux kernel, the following vulnerability has been resolved: nfc: pn533: Wait for out_urb's completion in pn533_usb_send_frame() Fix a use-after-free that occurs in hcd when in_urb sent from pn533_usb_send_frame() is completed earlier than out_urb. Its callback frees the skb data in pn533_send_async_complete() that is used as a transfer buffer of out_urb. Wait before sending in_urb until the callback of out_urb is called. To modify the callback of out_urb alone, separate the complete function of out_urb and ack_urb. Found by a modified version of syzkaller. BUG: KASAN: use-after-free in dummy_timer Call Trace: memcpy (mm/kasan/sha

    Publicación Actualización
  16. CVE-2023-52901

    Media · CVSS 5.5EPSS 0,24%Sin corrección publicada

    usb: xhci: Check endpoint is valid before dereferencing it

    In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Check endpoint is valid before dereferencing it When the host controller is not responding, all URBs queued to all endpoints need to be killed. This can cause a kernel panic if we dereference an invalid endpoint. Fix this by using xhci_get_virt_ep() helper to find the endpoint and checking if the endpoint is valid before dereferencing it. [233311.853271] xhci-hcd xhci-hcd.1.auto: xHCI host controller not responding, assume dead [233311.853393] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000e8 [233311.853964] pc : xhci_hc_died

    Publicación Actualización
  17. CVE-2023-52900

    Alta · CVSS 7.1EPSS 0,24%Sin corrección publicada

    nilfs2: fix general protection fault in nilfs_btree_insert()

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix general protection fault in nilfs_btree_insert() If nilfs2 reads a corrupted disk image and tries to reads a b-tree node block by calling __nilfs_btree_get_block() against an invalid virtual block address, it returns -ENOENT because conversion of the virtual block address to a disk block address fails. However, this return value is the same as the internal code that b-tree lookup routines return to indicate that the block being searched does not exist, so functions that operate on that b-tree may misbehave. When nilfs_btree_insert() receives this spurious 'not

    Publicación Actualización
  18. CVE-2023-52893

    Media · CVSS 5.5EPSS 0,24%Sin corrección publicada

    gsmi: fix null-deref in gsmi_get_variable

    In the Linux kernel, the following vulnerability has been resolved: gsmi: fix null-deref in gsmi_get_variable We can get EFI variables without fetching the attribute, so we must allow for that in gsmi. commit 859748255b43 ("efi: pstore: Omit efivars caching EFI varstore access layer") added a new get_variable call with attr=NULL, which triggers panic in gsmi.

    Publicación Actualización

Comprueba tu servidor

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

Comprueba tu servidor →