p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

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

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-49526

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

    md/bitmap: don't set sb values if can't pass sanity check

    In the Linux kernel, the following vulnerability has been resolved: md/bitmap: don't set sb values if can't pass sanity check If bitmap area contains invalid data, kernel will crash then mdadm triggers "Segmentation fault". This is cluster-md speical bug. In non-clustered env, mdadm will handle broken metadata case. In clustered array, only kernel space handles bitmap slot info. But even this bug only happened in clustered env, current sanity check is wrong, the code should be changed. How to trigger: (faulty injection) dd if=/dev/zero bs=1M count=1 oflag=direct of=/dev/sda dd if=/dev/zero bs=1M count=1 oflag=direct of=/dev/sdb mdadm -C /

    Veröffentlicht Aktualisiert
  2. CVE-2022-49525

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

    media: cx25821: Fix the warning when removing the module

    In the Linux kernel, the following vulnerability has been resolved: media: cx25821: Fix the warning when removing the module When removing the module, we will get the following warning: [ 14.746697] remove_proc_entry: removing non-empty directory 'irq/21', leaking at least 'cx25821[1]' [ 14.747449] WARNING: CPU: 4 PID: 368 at fs/proc/generic.c:717 remove_proc_entry+0x389/0x3f0 [ 14.751611] RIP: 0010:remove_proc_entry+0x389/0x3f0 [ 14.759589] Call Trace: [ 14.759792] <TASK> [ 14.759975] unregister_irq_proc+0x14c/0x170 [ 14.760340] irq_free_descs+0x94/0xe0 [ 14.760640] mp_unmap_irq+0xb6/0x100 [ 14.760937] acpi_unregist

    Veröffentlicht Aktualisiert
  3. CVE-2022-49522

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

    mmc: jz4740: Apply DMA engine limits to maximum segment size

    In the Linux kernel, the following vulnerability has been resolved: mmc: jz4740: Apply DMA engine limits to maximum segment size Do what is done in other DMA-enabled MMC host drivers (cf. host/mmci.c) and limit the maximum segment size based on the DMA engine's capabilities. This is needed to avoid warnings like the following with CONFIG_DMA_API_DEBUG=y. ------------[ cut here ]------------ WARNING: CPU: 0 PID: 21 at kernel/dma/debug.c:1162 debug_dma_map_sg+0x2f4/0x39c DMA-API: jz4780-dma 13420000.dma-controller: mapping sg segment longer than device claims to support [len=98304] [max=65536] CPU: 0 PID: 21 Comm: kworker/0:1H Not tainted 5.

    Veröffentlicht Aktualisiert
  4. CVE-2022-49521

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

    scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp()

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Fix resource leak in lpfc_sli4_send_seq_to_ulp() If no handler is found in lpfc_complete_unsol_iocb() to match the rctl of a received frame, the frame is dropped and resources are leaked. Fix by returning resources when discarding an unhandled frame type. Update lpfc_fc_frame_check() handling of NOP basic link service.

    Veröffentlicht Aktualisiert
  5. CVE-2022-49519

    Hoch · CVSS 8.8EPSS 0,35%Keine Korrektur veröffentlicht

    ath10k: skip ath10k_halt during suspend for driver state RESTARTING

    In the Linux kernel, the following vulnerability has been resolved: ath10k: skip ath10k_halt during suspend for driver state RESTARTING Double free crash is observed when FW recovery(caused by wmi timeout/crash) is followed by immediate suspend event. The FW recovery is triggered by ath10k_core_restart() which calls driver clean up via ath10k_halt(). When the suspend event occurs between the FW recovery, the restart worker thread is put into frozen state until suspend completes. The suspend event triggers ath10k_stop() which again triggers ath10k_halt() The double invocation of ath10k_halt() causes ath10k_htt_rx_free() to be called twice(No

    Veröffentlicht Aktualisiert
  6. CVE-2022-49504

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

    scsi: lpfc: Inhibit aborts if external loopback plug is inserted

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Inhibit aborts if external loopback plug is inserted After running a short external loopback test, when the external loopback is removed and a normal cable inserted that is directly connected to a target device, the system oops in the llpfc_set_rrq_active() routine. When the loopback was inserted an FLOGI was transmit. As we're looped back, we receive the FLOGI request. The FLOGI is ABTS'd as we recognize the same wppn thus understand it's a loopback. However, as the ABTS sends address information the port is not set to (fffffe), the ABTS is dropped on the wire

    Veröffentlicht Aktualisiert
  7. CVE-2022-49503

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

    ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix

    In the Linux kernel, the following vulnerability has been resolved: ath9k_htc: fix potential out of bounds access with invalid rxstatus->rs_keyix The "rxstatus->rs_keyix" eventually gets passed to test_bit() so we need to ensure that it is within the bitmap. drivers/net/wireless/ath/ath9k/common.c:46 ath9k_cmn_rx_accept() error: passing untrusted data 'rx_stats->rs_keyix' to 'test_bit()'

    Veröffentlicht Aktualisiert
  8. CVE-2022-49497

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

    net: remove two BUG() from skb_checksum_help()

    In the Linux kernel, the following vulnerability has been resolved: net: remove two BUG() from skb_checksum_help() I have a syzbot report that managed to get a crash in skb_checksum_help() If syzbot can trigger these BUG(), it makes sense to replace them with more friendly WARN_ON_ONCE() since skb_checksum_help() can instead return an error code. Note that syzbot will still crash there, until real bug is fixed.

    Veröffentlicht Aktualisiert
  9. CVE-2022-49495

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

    drm/msm/hdmi: check return value after calling platform_get_resource_byname()

    In the Linux kernel, the following vulnerability has been resolved: drm/msm/hdmi: check return value after calling platform_get_resource_byname() It will cause null-ptr-deref if platform_get_resource_byname() returns NULL, we need check the return value. Patchwork: https://patchwork.freedesktop.org/patch/482992/

    Veröffentlicht Aktualisiert
  10. CVE-2022-49492

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

    nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags

    In the Linux kernel, the following vulnerability has been resolved: nvme-pci: fix a NULL pointer dereference in nvme_alloc_admin_tags In nvme_alloc_admin_tags, the admin_q can be set to an error (typically -ENOMEM) if the blk_mq_init_queue call fails to set up the queue, which is checked immediately after the call. However, when we return the error message up the stack, to nvme_reset_work the error takes us to nvme_remove_dead_ctrl() nvme_dev_disable() nvme_suspend_queue(&dev->queues[0]). Here, we only check that the admin_q is non-NULL, rather than not an error or NULL, and begin quiescing a queue that never existed, leading to bad /

    Veröffentlicht Aktualisiert
  11. CVE-2022-49491

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

    drm/rockchip: vop: fix possible null-ptr-deref in vop_bind()

    In the Linux kernel, the following vulnerability has been resolved: drm/rockchip: vop: fix possible null-ptr-deref in vop_bind() It will cause null-ptr-deref in resource_size(), if platform_get_resource() returns NULL, move calling resource_size() after devm_ioremap_resource() that will check 'res' to avoid null-ptr-deref.

    Veröffentlicht Aktualisiert
  12. CVE-2022-49486

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

    ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe

    In the Linux kernel, the following vulnerability has been resolved: ASoC: fsl: Fix refcount leak in imx_sgtl5000_probe of_find_i2c_device_by_node() takes a reference, In error paths, we should call put_device() to drop the reference to aviod refount leak.

    Veröffentlicht Aktualisiert
  13. CVE-2022-49482

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

    ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe

    In the Linux kernel, the following vulnerability has been resolved: ASoC: mxs-saif: Fix refcount leak in mxs_saif_probe of_parse_phandle() returns a node pointer with refcount incremented, we should use of_node_put() on it when done.

    Veröffentlicht Aktualisiert
  14. CVE-2022-49481

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

    regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt

    In the Linux kernel, the following vulnerability has been resolved: regulator: pfuze100: Fix refcount leak in pfuze_parse_regulators_dt of_node_get() returns a node with refcount incremented. Calling of_node_put() to drop the reference when not needed anymore.

    Veröffentlicht Aktualisiert
  15. CVE-2022-49478

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

    media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init

    In the Linux kernel, the following vulnerability has been resolved: media: pvrusb2: fix array-index-out-of-bounds in pvr2_i2c_core_init Syzbot reported that -1 is used as array index. The problem was in missing validation check. hdw->unit_number is initialized with -1 and then if init table walk fails this value remains unchanged. Since code blindly uses this member for array indexing adding sanity check is the easiest fix for that. hdw->workpoll initialization moved upper to prevent warning in __flush_work.

    Veröffentlicht Aktualisiert
  16. CVE-2022-49472

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

    net: phy: micrel: Allow probing without .driver_data

    In the Linux kernel, the following vulnerability has been resolved: net: phy: micrel: Allow probing without .driver_data Currently, if the .probe element is present in the phy_driver structure and the .driver_data is not, a NULL pointer dereference happens. Allow passing .probe without .driver_data by inserting NULL checks for priv->type.

    Veröffentlicht Aktualisiert
  17. CVE-2022-49467

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

    drm: msm: fix possible memory leak in mdp5_crtc_cursor_set()

    In the Linux kernel, the following vulnerability has been resolved: drm: msm: fix possible memory leak in mdp5_crtc_cursor_set() drm_gem_object_lookup will call drm_gem_object_get inside. So cursor_bo needs to be put when msm_gem_get_and_pin_iova fails.

    Veröffentlicht Aktualisiert
  18. CVE-2022-49465

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

    blk-throttle: Set BIO_THROTTLED when bio has been throttled

    In the Linux kernel, the following vulnerability has been resolved: blk-throttle: Set BIO_THROTTLED when bio has been throttled 1.In current process, all bio will set the BIO_THROTTLED flag after __blk_throtl_bio(). 2.If bio needs to be throttled, it will start the timer and stop submit bio directly. Bio will submit in blk_throtl_dispatch_work_fn() when the timer expires.But in the current process, if bio is throttled. The BIO_THROTTLED will be set to bio after timer start. If the bio has been completed, it may cause use-after-free blow. BUG: KASAN: use-after-free in blk_throtl_bio+0x12f0/0x2c70 Read of size 2 at addr ffff88801b8902d4 by

    Veröffentlicht Aktualisiert
  19. CVE-2022-49457

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

    ARM: versatile: Add missing of_node_put in dcscb_init

    In the Linux kernel, the following vulnerability has been resolved: ARM: versatile: Add missing of_node_put in dcscb_init The device_node pointer is returned by of_find_compatible_node with refcount incremented. We should use of_node_put() to avoid the refcount leak.

    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 →