p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-intel-iotg-5.15 · Seite 161

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-intel-iotg-5.15: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4693

  1. CVE-2022-48865

    Mittel · CVSS 5.7EPSS 0,26%Korrektur verfügbar

    tipc: fix kernel panic when enabling bearer

    In the Linux kernel, the following vulnerability has been resolved: tipc: fix kernel panic when enabling bearer When enabling a bearer on a node, a kernel panic is observed: [ 4.498085] RIP: 0010:tipc_mon_prep+0x4e/0x130 [tipc] ... [ 4.520030] Call Trace: [ 4.520689] <IRQ> [ 4.521236] tipc_link_build_proto_msg+0x375/0x750 [tipc] [ 4.522654] tipc_link_build_state_msg+0x48/0xc0 [tipc] [ 4.524034] __tipc_node_link_up+0xd7/0x290 [tipc] [ 4.525292] tipc_rcv+0x5da/0x730 [tipc] [ 4.526346] ? __netif_receive_skb_core+0xb7/0xfc0 [ 4.527601] tipc_l2_rcv_msg+0x5e/0x90 [tipc] [ 4.528737] __netif_receive_skb_list_c

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-48864

    Hoch · CVSS 8.8EPSS 0,25%Korrektur verfügbar

    vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command

    In the Linux kernel, the following vulnerability has been resolved: vdpa/mlx5: add validation for VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command When control vq receives a VIRTIO_NET_CTRL_MQ_VQ_PAIRS_SET command request from the driver, presently there is no validation against the number of queue pairs to configure, or even if multiqueue had been negotiated or not is unverified. This may lead to kernel panic due to uninitialized resource for the queues were there any bogus request sent down by untrusted driver. Tie up the loose ends there.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2022-48863

    Mittel · CVSS 6.8EPSS 0,25%Korrektur verfügbar

    mISDN: Fix memory leak in dsp_pipeline_build()

    In the Linux kernel, the following vulnerability has been resolved: mISDN: Fix memory leak in dsp_pipeline_build() dsp_pipeline_build() allocates dup pointer by kstrdup(cfg), but then it updates dup variable by strsep(&dup, "|"). As a result when it calls kfree(dup), the dup variable contains NULL. Found by Linux Driver Verification project (linuxtesting.org) with SVACE.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2022-48862

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    vhost: fix hung thread due to erroneous iotlb entries

    In the Linux kernel, the following vulnerability has been resolved: vhost: fix hung thread due to erroneous iotlb entries In vhost_iotlb_add_range_ctx(), range size can overflow to 0 when start is 0 and last is ULONG_MAX. One instance where it can happen is when userspace sends an IOTLB message with iova=size=uaddr=0 (vhost_process_iotlb_msg). So, an entry with size = 0, start = 0, last = ULONG_MAX ends up in the iotlb. Next time a packet is sent, iotlb_access_ok() loops indefinitely due to that erroneous entry. Call Trace: <TASK> iotlb_access_ok+0x21b/0x3e0 drivers/vhost/vhost.c:1340 vq_meta_prefetch+0xbc/0x280 drivers/vhost/vhost.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2022-48861

    Mittel · CVSS 5.5EPSS 0,2%Korrektur verfügbar

    vdpa: fix use-after-free on vp_vdpa_remove

    In the Linux kernel, the following vulnerability has been resolved: vdpa: fix use-after-free on vp_vdpa_remove When vp_vdpa driver is unbind, vp_vdpa is freed in vdpa_unregister_device and then vp_vdpa->mdev.pci_dev is dereferenced in vp_modern_remove, triggering use-after-free. Call Trace of unbinding driver free vp_vdpa : do_syscall_64 vfs_write kernfs_fop_write_iter device_release_driver_internal pci_device_remove vp_vdpa_remove vdpa_unregister_device kobject_release device_release kfree Call Trace of dereference vp_vdpa->mdev.pci_dev: vp_modern_r

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2022-48860

    Mittel · CVSS 5.5EPSS 0,22%Korrektur verfügbar

    ethernet: Fix error handling in xemaclite_of_probe

    In the Linux kernel, the following vulnerability has been resolved: ethernet: Fix error handling in xemaclite_of_probe This node pointer is returned by of_parse_phandle() with refcount incremented in this function. Calling of_node_put() to avoid the refcount leak. As the remove function do.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2022-48859

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr

    In the Linux kernel, the following vulnerability has been resolved: net: marvell: prestera: Add missing of_node_put() in prestera_switch_set_base_mac_addr This node pointer is returned by of_find_compatible_node() with refcount incremented. Calling of_node_put() to aovid the refcount leak.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2022-48858

    Hoch · CVSS 7EPSS 0,18%Korrektur verfügbar

    net/mlx5: Fix a race on command flush flow

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Fix a race on command flush flow Fix a refcount use after free warning due to a race on command entry. Such race occurs when one of the commands releases its last refcount and frees its index and entry while another process running command flush flow takes refcount to this command entry. The process which handles commands flush may see this command as needed to be flushed if the other process released its refcount but didn't release the index yet. Fix it by adding the needed spin lock. It fixes the following warning trace: refcount_t: addition on 0; use-after-fr

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2022-48857

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    NFC: port100: fix use-after-free in port100_send_complete

    In the Linux kernel, the following vulnerability has been resolved: NFC: port100: fix use-after-free in port100_send_complete Syzbot reported UAF in port100_send_complete(). The root case is in missing usb_kill_urb() calls on error handling path of ->probe function. port100_send_complete() accesses devm allocated memory which will be freed on probe failure. We should kill this urbs before returning an error from probe function to prevent reported use-after-free Fail log: BUG: KASAN: use-after-free in port100_send_complete+0x16e/0x1a0 drivers/nfc/port100.c:935 Read of size 1 at addr ffff88801bb59540 by task ksoftirqd/2/26 ... Call Trace:

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2022-48856

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    gianfar: ethtool: Fix refcount leak in gfar_get_ts_info

    In the Linux kernel, the following vulnerability has been resolved: gianfar: ethtool: Fix refcount leak in gfar_get_ts_info The of_find_compatible_node() function returns a node pointer with refcount incremented, We should use of_node_put() on it when done Add the missing of_node_put() to release the refcount.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2022-48855

    Hoch · CVSS 7.1EPSS 0,23%Korrektur verfügbar

    sctp: fix kernel-infoleak for SCTP sockets

    In the Linux kernel, the following vulnerability has been resolved: sctp: fix kernel-infoleak for SCTP sockets syzbot reported a kernel infoleak [1] of 4 bytes. After analysis, it turned out r->idiag_expires is not initialized if inet_sctp_diag_fill() calls inet_diag_msg_common_fill() Make sure to clear idiag_timer/idiag_retrans/idiag_expires and let inet_diag_msg_sctpasoc_fill() fill them again if needed. [1] BUG: KMSAN: kernel-infoleak in instrument_copy_to_user include/linux/instrumented.h:121 [inline] BUG: KMSAN: kernel-infoleak in copyout lib/iov_iter.c:154 [inline] BUG: KMSAN: kernel-infoleak in _copy_to_iter+0x6ef/0x25a0 lib/iov_

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2022-48853

    Mittel · CVSS 5.5EPSS 0,27%Korrektur verfügbar

    Reinstate some of "swiotlb: rework "fix info leak with DMA_FROM_DEVICE""

    In the Linux kernel, the following vulnerability has been resolved: swiotlb: fix info leak with DMA_FROM_DEVICE The problem I'm addressing was discovered by the LTP test covering cve-2018-1000204. A short description of what happens follows: 1) The test case issues a command code 00 (TEST UNIT READY) via the SG_IO interface with: dxfer_len == 524288, dxdfer_dir == SG_DXFER_FROM_DEV and a corresponding dxferp. The peculiar thing about this is that TUR is not reading from the device. 2) In sg_start_req() the invocation of blk_rq_map_user() effectively bounces the user-space buffer. As if the device was to transfer into it. Sin

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2022-48852

    Niedrig · CVSS 3.3EPSS 0,2%Korrektur verfügbar

    drm/vc4: hdmi: Unregister codec device on unbind

    In the Linux kernel, the following vulnerability has been resolved: drm/vc4: hdmi: Unregister codec device on unbind On bind we will register the HDMI codec device but we don't unregister it on unbind, leading to a device leakage. Unregister our device at unbind.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2022-48851

    Kritisch · CVSS 9.8EPSS 0,51%Korrektur verfügbar

    staging: gdm724x: fix use after free in gdm_lte_rx()

    In the Linux kernel, the following vulnerability has been resolved: staging: gdm724x: fix use after free in gdm_lte_rx() The netif_rx_ni() function frees the skb so we can't dereference it to save the skb->len.

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2022-48850

    Mittel · CVSS 5.5EPSS 0,21%Korrektur verfügbar

    net-sysfs: add check for netdevice being present to speed_show

    In the Linux kernel, the following vulnerability has been resolved: net-sysfs: add check for netdevice being present to speed_show When bringing down the netdevice or system shutdown, a panic can be triggered while accessing the sysfs path because the device is already removed. [ 755.549084] mlx5_core 0000:12:00.1: Shutdown was called [ 756.404455] mlx5_core 0000:12:00.0: Shutdown was called ... [ 757.937260] BUG: unable to handle kernel NULL pointer dereference at (null) [ 758.031397] IP: [<ffffffff8ee11acb>] dma_pool_alloc+0x1ab/0x280 crash> bt ... PID: 12649 TASK: ffff8924108f2100 CPU: 1

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2022-48847

    Hoch · CVSS 7.8EPSS 0,24%Korrektur verfügbar

    watch_queue: Fix filter limit check

    In the Linux kernel, the following vulnerability has been resolved: watch_queue: Fix filter limit check In watch_queue_set_filter(), there are a couple of places where we check that the filter type value does not exceed what the type_filter bitmap can hold. One place calculates the number of bits by: if (tf[i].type >= sizeof(wfilter->type_filter) * 8) which is fine, but the second does: if (tf[i].type >= sizeof(wfilter->type_filter) * BITS_PER_LONG) which is not. This can lead to a couple of out-of-bounds writes due to a too-large type: (1) __set_bit() on wfilter->type_filter (2) Writing more elements in wfilter->filters[] th

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2022-48846

    Mittel · CVSS 5.5EPSS 0,22%Korrektur verfügbar

    block: release rq qos structures for queue without disk

    In the Linux kernel, the following vulnerability has been resolved: block: release rq qos structures for queue without disk blkcg_init_queue() may add rq qos structures to request queue, previously blk_cleanup_queue() calls rq_qos_exit() to release them, but commit 8e141f9eb803 ("block: drain file system I/O on del_gendisk") moves rq_qos_exit() into del_gendisk(), so memory leak is caused because queues may not have disk, such as un-present scsi luns, nvme admin queue, ... Fixes the issue by adding rq_qos_exit() to blk_cleanup_queue() back. BTW, v5.18 won't need this patch any more since we move blkcg_init_queue()/blkcg_exit_queue() into

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2022-48845

    Mittel · CVSS 5.5EPSS 0,22%Korrektur verfügbar

    MIPS: smp: fill in sibling and core maps earlier

    In the Linux kernel, the following vulnerability has been resolved: MIPS: smp: fill in sibling and core maps earlier After enabling CONFIG_SCHED_CORE (landed during 5.14 cycle), 2-core 2-thread-per-core interAptiv (CPS-driven) started emitting the following: [ 0.025698] CPU1 revision is: 0001a120 (MIPS interAptiv (multi)) [ 0.048183] ------------[ cut here ]------------ [ 0.048187] WARNING: CPU: 1 PID: 0 at kernel/sched/core.c:6025 sched_core_cpu_starting+0x198/0x240 [ 0.048220] Modules linked in: [ 0.048233] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.17.0-rc3+ #35 b7b319f24073fd9a3c2aa7ad15fb7993eec0b26f [ 0.048247] Sta

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2022-48839

    Hoch · CVSS 7.8EPSS 0,27%Korrektur verfügbar

    net/packet: fix slab-out-of-bounds access in packet_recvmsg()

    In the Linux kernel, the following vulnerability has been resolved: net/packet: fix slab-out-of-bounds access in packet_recvmsg() syzbot found that when an AF_PACKET socket is using PACKET_COPY_THRESH and mmap operations, tpacket_rcv() is queueing skbs with garbage in skb->cb[], triggering a too big copy [1] Presumably, users of af_packet using mmap() already gets correct metadata from the mapped buffer, we can simply make sure to clear 12 bytes that might be copied to user space later. BUG: KASAN: stack-out-of-bounds in memcpy include/linux/fortify-string.h:225 [inline] BUG: KASAN: stack-out-of-bounds in packet_recvmsg+0x56c/0x1150 net/p

    • Auf 5.15.0-1008.11~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →