p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-lts-xenial · Seite 169

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für linux-lts-xenial: 333. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 5474

  1. CVE-2022-49725

    Hoch · CVSS 7.8EPSS 0,3%Keine Korrektur veröffentlicht

    i40e: Fix call trace in setup_tx_descriptors

    In the Linux kernel, the following vulnerability has been resolved: i40e: Fix call trace in setup_tx_descriptors After PF reset and ethtool -t there was call trace in dmesg sometimes leading to panic. When there was some time, around 5 seconds, between reset and test there were no errors. Problem was that pf reset calls i40e_vsi_close in prep_for_reset and ethtool -t calls i40e_vsi_close in diag_test. If there was not enough time between those commands the second i40e_vsi_close starts before previous i40e_vsi_close was done which leads to crash. Add check to diag_test if pf is in reset and don't start offline tests if it is true. Add neti

    Veröffentlicht Aktualisiert
  2. CVE-2022-49712

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    usb: gadget: lpc32xx_udc: Fix refcount leak in lpc32xx_udc_probe

    In the Linux kernel, the following vulnerability has been resolved: usb: gadget: lpc32xx_udc: Fix refcount leak in lpc32xx_udc_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. of_node_put() will check NULL pointer.

    Veröffentlicht Aktualisiert
  3. CVE-2022-49710

    Mittel · CVSS 5.5EPSS 0,28%Keine Korrektur veröffentlicht

    dm mirror log: round up region bitmap size to BITS_PER_LONG

    In the Linux kernel, the following vulnerability has been resolved: dm mirror log: round up region bitmap size to BITS_PER_LONG The code in dm-log rounds up bitset_size to 32 bits. It then uses find_next_zero_bit_le on the allocated region. find_next_zero_bit_le accesses the bitmap using unsigned long pointers. So, on 64-bit architectures, it may access 4 bytes beyond the allocated size. Fix this bug by rounding up bitset_size to BITS_PER_LONG. This bug was found by running the lvm2 testsuite with kasan.

    Veröffentlicht Aktualisiert
  4. CVE-2022-49708

    Hoch · CVSS 7.1EPSS 0,28%Keine Korrektur veröffentlicht

    ext4: fix bug_on ext4_mb_use_inode_pa

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug_on ext4_mb_use_inode_pa Hulk Robot reported a BUG_ON: ================================================================== kernel BUG at fs/ext4/mballoc.c:3211! [...] RIP: 0010:ext4_mb_mark_diskspace_used.cold+0x85/0x136f [...] Call Trace: ext4_mb_new_blocks+0x9df/0x5d30 ext4_ext_map_blocks+0x1803/0x4d80 ext4_map_blocks+0x3a4/0x1a10 ext4_writepages+0x126d/0x2c30 do_writepages+0x7f/0x1b0 __filemap_fdatawrite_range+0x285/0x3b0 file_write_and_wait_range+0xb1/0x140 ext4_sync_file+0x1aa/0xca0 vfs_fsync_range+0xfb/0x260 do_fsync+0x48/0xa0 [...] =============

    Veröffentlicht Aktualisiert
  5. CVE-2022-49707

    Mittel · CVSS 5.5EPSS 0,28%Keine Korrektur veröffentlicht

    ext4: add reserved GDT blocks check

    In the Linux kernel, the following vulnerability has been resolved: ext4: add reserved GDT blocks check We capture a NULL pointer issue when resizing a corrupt ext4 image which is freshly clear resize_inode feature (not run e2fsck). It could be simply reproduced by following steps. The problem is because of the resize_inode feature was cleared, and it will convert the filesystem to meta_bg mode in ext4_resize_fs(), but the es->s_reserved_gdt_blocks was not reduced to zero, so could we mistakenly call reserve_backup_gdb() and passing an uninitialized resize_inode to it when adding new group descriptors. mkfs.ext4 /dev/sda 3G tune2fs -O ^r

    Veröffentlicht Aktualisiert
  6. CVE-2022-49700

    Hoch · CVSS 7.8EPSS 0,29%Keine Korrektur veröffentlicht

    mm/slub: add missing TID updates on slab deactivation

    In the Linux kernel, the following vulnerability has been resolved: mm/slub: add missing TID updates on slab deactivation The fastpath in slab_alloc_node() assumes that c->slab is stable as long as the TID stays the same. However, two places in __slab_alloc() currently don't update the TID when deactivating the CPU slab. If multiple operations race the right way, this could lead to an object getting lost; or, in an even more unlikely situation, it could even lead to an object being freed onto the wrong slab's freelist, messing up the `inuse` counter and eventually causing a page to be freed to the page allocator while it still contains sla

    Veröffentlicht Aktualisiert
  7. CVE-2022-49685

    Hoch · CVSS 7.8EPSS 0,28%Keine Korrektur veröffentlicht

    iio: trigger: sysfs: fix use-after-free on remove

    In the Linux kernel, the following vulnerability has been resolved: iio: trigger: sysfs: fix use-after-free on remove Ensure that the irq_work has completed before the trigger is freed. ================================================================== BUG: KASAN: use-after-free in irq_work_run_list Read of size 8 at addr 0000000064702248 by task python3/25 Call Trace: irq_work_run_list irq_work_tick update_process_times tick_sched_handle tick_sched_timer __hrtimer_run_queues hrtimer_interrupt Allocated by task 25: kmem_cache_alloc_trace iio_sysfs_trig_add dev_attr_store sysfs_kf_write kernfs_fop_write_iter

    Veröffentlicht Aktualisiert
  8. CVE-2022-49681

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    xtensa: xtfpga: Fix refcount leak bug in setup

    In the Linux kernel, the following vulnerability has been resolved: xtensa: xtfpga: Fix refcount leak bug in setup In machine_setup(), of_find_compatible_node() will return a node pointer with refcount incremented. We should use of_node_put() when it is not used anymore.

    Veröffentlicht Aktualisiert
  9. CVE-2022-49680

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    ARM: exynos: Fix refcount leak in exynos_map_pmu

    In the Linux kernel, the following vulnerability has been resolved: ARM: exynos: Fix refcount leak in exynos_map_pmu of_find_matching_node() returns a node pointer with refcount incremented, we should use of_node_put() on it when not need anymore. Add missing of_node_put() to avoid refcount leak. of_node_put() checks null pointer.

    Veröffentlicht Aktualisiert
  10. CVE-2022-49679

    Mittel · CVSS 5.5EPSS 0,27%Keine Korrektur veröffentlicht

    ARM: Fix refcount leak in axxia_boot_secondary

    In the Linux kernel, the following vulnerability has been resolved: ARM: Fix refcount leak in axxia_boot_secondary of_find_compatible_node() 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.

    Veröffentlicht Aktualisiert
  11. CVE-2022-49677

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    ARM: cns3xxx: Fix refcount leak in cns3xxx_init

    In the Linux kernel, the following vulnerability has been resolved: ARM: cns3xxx: Fix refcount leak in cns3xxx_init of_find_compatible_node() 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.

    Veröffentlicht Aktualisiert
  12. CVE-2022-49673

    Mittel · CVSS 5.5EPSS 0,28%Keine Korrektur veröffentlicht

    dm raid: fix KASAN warning in raid5_add_disks

    In the Linux kernel, the following vulnerability has been resolved: dm raid: fix KASAN warning in raid5_add_disks There's a KASAN warning in raid5_add_disk when running the LVM testsuite. The warning happens in the test lvconvert-raid-reshape-linear_to_raid6-single-type.sh. We fix the warning by verifying that rdev->saved_raid_disk is within limits.

    Veröffentlicht Aktualisiert
  13. CVE-2022-49668

    Mittel · CVSS 5.5EPSS 0,26%Keine Korrektur veröffentlicht

    PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events

    In the Linux kernel, the following vulnerability has been resolved: PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events of_get_child_by_name() returns a node pointer with refcount incremented, we should use of_node_put() on it when done. This function only calls of_node_put() in normal path, missing it in error paths. Add missing of_node_put() to avoid refcount leak.

    Veröffentlicht Aktualisiert
  14. CVE-2022-49667

    Hoch · CVSS 7.8EPSS 0,29%Keine Korrektur veröffentlicht

    net: bonding: fix use-after-free after 802.3ad slave unbind

    In the Linux kernel, the following vulnerability has been resolved: net: bonding: fix use-after-free after 802.3ad slave unbind commit 0622cab0341c ("bonding: fix 802.3ad aggregator reselection"), resolve case, when there is several aggregation groups in the same bond. bond_3ad_unbind_slave will invalidate (clear) aggregator when __agg_active_ports return zero. So, ad_clear_agg can be executed even, when num_of_ports!=0. Than bond_3ad_unbind_slave can be executed again for, previously cleared aggregator. NOTE: at this time bond_3ad_unbind_slave will not update slave ports list, because lag_ports==NULL. So, here we got slave ports, pointing

    Veröffentlicht Aktualisiert
  15. CVE-2022-49661

    Mittel · CVSS 5.5EPSS 0,27%Keine Korrektur veröffentlicht

    can: gs_usb: gs_usb_open/close(): fix memory leak

    In the Linux kernel, the following vulnerability has been resolved: can: gs_usb: gs_usb_open/close(): fix memory leak The gs_usb driver appears to suffer from a malady common to many USB CAN adapter drivers in that it performs usb_alloc_coherent() to allocate a number of USB request blocks (URBs) for RX, and then later relies on usb_kill_anchored_urbs() to free them, but this doesn't actually free them. As a result, this may be leaking DMA memory that's been used by the driver. This commit is an adaptation of the techniques found in the esd_usb2 driver where a similar design pattern led to a memory leak. It explicitly frees the RX URBs and

    Veröffentlicht Aktualisiert
  16. CVE-2022-49657

    Mittel · CVSS 5.5EPSS 0,28%Keine Korrektur veröffentlicht

    usbnet: fix memory leak in error case

    In the Linux kernel, the following vulnerability has been resolved: usbnet: fix memory leak in error case usbnet_write_cmd_async() mixed up which buffers need to be freed in which error case. v2: add Fixes tag v3: fix uninitialized buf pointer

    Veröffentlicht Aktualisiert
  17. CVE-2022-49647

    Hoch · CVSS 7.8EPSS 0,29%Keine Korrektur veröffentlicht

    cgroup: Use separate src/dst nodes when preloading css_sets for migration

    In the Linux kernel, the following vulnerability has been resolved: cgroup: Use separate src/dst nodes when preloading css_sets for migration Each cset (css_set) is pinned by its tasks. When we're moving tasks around across csets for a migration, we need to hold the source and destination csets to ensure that they don't go away while we're moving tasks about. This is done by linking cset->mg_preload_node on either the mgctx->preloaded_src_csets or mgctx->preloaded_dst_csets list. Using the same cset->mg_preload_node for both the src and dst lists was deemed okay as a cset can't be both the source and destination at the same time. Unfortuna

    Veröffentlicht Aktualisiert
  18. CVE-2022-49641

    Mittel · CVSS 4.7EPSS 0,18%Keine Korrektur veröffentlicht

    sysctl: Fix data races in proc_douintvec().

    In the Linux kernel, the following vulnerability has been resolved: sysctl: Fix data races in proc_douintvec(). A sysctl variable is accessed concurrently, and there is always a chance of data-race. So, all readers and writers need some basic protection to avoid load/store-tearing. This patch changes proc_douintvec() to use READ_ONCE() and WRITE_ONCE() internally to fix data-races on the sysctl side. For now, proc_douintvec() itself is tolerant to a data-race, but we still need to add annotations on the other subsystem's side.

    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 →