p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

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

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: 4699

  1. CVE-2022-50561

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    iio: fix memory leak in iio_device_register_eventset()

    In the Linux kernel, the following vulnerability has been resolved: iio: fix memory leak in iio_device_register_eventset() When iio_device_register_sysfs_group() returns failed, iio_device_register_eventset() needs to free attrs array. Otherwise, kmemleak would scan & report memory leak as below: unreferenced object 0xffff88810a1cc3c0 (size 32): comm "100-i2c-vcnl302", pid 728, jiffies 4295052307 (age 156.027s) backtrace: __kmalloc+0x46/0x1b0 iio_device_register_eventset at drivers/iio/industrialio-event.c:541 __iio_device_register at drivers/iio/industrialio-core.c:1959 __devm_iio_device_register at drivers/iio/indust

    • Auf 5.15.0-1027.32~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2022-50560

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    drm/meson: explicitly remove aggregate driver at module unload time

    In the Linux kernel, the following vulnerability has been resolved: drm/meson: explicitly remove aggregate driver at module unload time Because component_master_del wasn't being called when unloading the meson_drm module, the aggregate device would linger forever in the global aggregate_devices list. That means when unloading and reloading the meson_dw_hdmi module, component_add would call into try_to_bring_up_aggregate_device and find the unbound meson_drm aggregate device. This would in turn dereference some of the aggregate_device's struct entries which point to memory automatically freed by the devres API when unbinding the aggregate d

    • Auf 5.15.0-1025.30~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2022-50559

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    clk: imx: scu: fix memleak on platform_device_add() fails

    In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: fix memleak on platform_device_add() fails No error handling is performed when platform_device_add() fails. Add error processing before return, and modified the return value.

    • Auf 5.15.0-1025.30~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2022-50556

    Nicht bewertetEPSS 0,21%Korrektur verfügbar

    drm: Fix potential null-ptr-deref due to drmm_mode_config_init()

    In the Linux kernel, the following vulnerability has been resolved: drm: Fix potential null-ptr-deref due to drmm_mode_config_init() drmm_mode_config_init() will call drm_mode_create_standard_properties() and won't check the ret value. When drm_mode_create_standard_properties() failed due to alloc, property will be a NULL pointer and may causes the null-ptr-deref. Fix the null-ptr-deref by adding the ret value check. Found null-ptr-deref while testing insert module bochs: general protection fault, probably for non-canonical address 0xdffffc000000000c: 0000 [#1] SMP KASAN PTI KASAN: null-ptr-deref in range [0x0000000000000060-0x00000000

    • Auf 5.15.0-1033.38~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-53687

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

    tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk

    In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung_tty: Fix a memory leak in s3c24xx_serial_getclk() when iterating clk When the best clk is searched, we iterate over all possible clk. If we find a better match, the previous one, if any, needs to be freed. If a better match has already been found, we still need to free the new one, otherwise it leaks.

    • Auf 5.15.0-1043.49~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2023-53684

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

    xfrm: Zero padding when dumping algos and encap

    In the Linux kernel, the following vulnerability has been resolved: xfrm: Zero padding when dumping algos and encap When copying data to user-space we should ensure that only valid data is copied over. Padding in structures may be filled with random (possibly sensitve) data and should never be given directly to user-space. This patch fixes the copying of xfrm algorithms and the encap template in xfrm_user so that padding is zeroed.

    • Auf 5.15.0-1037.42~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2023-53683

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

    fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode()

    In the Linux kernel, the following vulnerability has been resolved: fs: hfsplus: remove WARN_ON() from hfsplus_cat_{read,write}_inode() syzbot is hitting WARN_ON() in hfsplus_cat_{read,write}_inode(), for crafted filesystem image can contain bogus length. There conditions are not kernel bugs that can justify kernel to panic.

    • Auf 5.15.0-1040.46~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2023-53681

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

    bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent

    In the Linux kernel, the following vulnerability has been resolved: bcache: Fix __bch_btree_node_alloc to make the failure behavior consistent In some specific situations, the return value of __bch_btree_node_alloc may be NULL. This may lead to a potential NULL pointer dereference in caller function like a calling chain : btree_split->bch_btree_node_alloc->__bch_btree_node_alloc. Fix it by initializing the return value in __bch_btree_node_alloc.

    • Auf 5.15.0-1043.49~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2023-53680

    Hoch · CVSS 7.5EPSS 0,3%Korrektur verfügbar

    NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL

    In the Linux kernel, the following vulnerability has been resolved: NFSD: Avoid calling OPDESC() with ops->opnum == OP_ILLEGAL OPDESC() simply indexes into nfsd4_ops[] by the op's operation number, without range checking that value. It assumes callers are careful to avoid calling it with an out-of-bounds opnum value. nfsd4_decode_compound() is not so careful, and can invoke OPDESC() with opnum set to OP_ILLEGAL, which is 10044 -- well beyond the end of nfsd4_ops[].

    • Auf 5.15.0-1037.42~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2023-53679

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

    wifi: mt7601u: fix an integer underflow

    In the Linux kernel, the following vulnerability has been resolved: wifi: mt7601u: fix an integer underflow Fix an integer underflow that leads to a null pointer dereference in 'mt7601u_rx_skb_from_seg()'. The variable 'dma_len' in the URB packet could be manipulated, which could trigger an integer underflow of 'seg_len' in 'mt7601u_rx_process_seg()'. This underflow subsequently causes the 'bad_frame' checks in 'mt7601u_rx_skb_from_seg()' to be bypassed, eventually leading to a dereference of the pointer 'p', which is a null pointer. Ensure that 'dma_len' is greater than 'min_seg_len'. Found by a modified version of syzkaller. KASAN: nul

    • Auf 5.15.0-1033.38~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2023-53676

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

    scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show()

    In the Linux kernel, the following vulnerability has been resolved: scsi: target: iscsi: Fix buffer overflow in lio_target_nacl_info_show() The function lio_target_nacl_info_show() uses sprintf() in a loop to print details for every iSCSI connection in a session without checking for the buffer length. With enough iSCSI connections it's possible to overflow the buffer provided by configfs and corrupt the memory. This patch replaces sprintf() with sysfs_emit_at() that checks for buffer boundries.

    • Auf 5.15.0-1048.54~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2023-53675

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

    scsi: ses: Fix possible desc_ptr out-of-bounds accesses

    In the Linux kernel, the following vulnerability has been resolved: scsi: ses: Fix possible desc_ptr out-of-bounds accesses Sanitize possible desc_ptr out-of-bounds accesses in ses_enclosure_data_process().

    • Auf 5.15.0-1033.38~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2023-53674

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

    clk: Fix memory leak in devm_clk_notifier_register()

    In the Linux kernel, the following vulnerability has been resolved: clk: Fix memory leak in devm_clk_notifier_register() devm_clk_notifier_register() allocates a devres resource for clk notifier but didn't register that to the device, so the notifier didn't get unregistered on device detach and the allocated resource was leaked. Fix the issue by registering the resource through devres_add(). This issue was found with kmemleak on a Chromebook.

    • Auf 5.15.0-1043.49~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2023-53672

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

    btrfs: output extra debug info if we failed to find an inline backref

    In the Linux kernel, the following vulnerability has been resolved: btrfs: output extra debug info if we failed to find an inline backref [BUG] Syzbot reported several warning triggered inside lookup_inline_extent_backref(). [CAUSE] As usual, the reproducer doesn't reliably trigger locally here, but at least we know the WARN_ON() is triggered when an inline backref can not be found, and it can only be triggered when @insert is true. (I.e. inserting a new inline backref, which means the backref should already exist) [ENHANCEMENT] After the WARN_ON(), dump all the parameters and the extent tree leaf to help debug.

    • Auf 5.15.0-1048.54~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2023-53668

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

    ring-buffer: Fix deadloop issue on reading trace_pipe

    In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Fix deadloop issue on reading trace_pipe Soft lockup occurs when reading file 'trace_pipe': watchdog: BUG: soft lockup - CPU#6 stuck for 22s! [cat:4488] [...] RIP: 0010:ring_buffer_empty_cpu+0xed/0x170 RSP: 0018:ffff88810dd6fc48 EFLAGS: 00000246 RAX: 0000000000000000 RBX: 0000000000000246 RCX: ffffffff93d1aaeb RDX: ffff88810a280040 RSI: 0000000000000008 RDI: ffff88811164b218 RBP: ffff88811164b218 R08: 0000000000000000 R09: ffff88815156600f R10: ffffed102a2acc01 R11: 0000000000000001 R12: 0000000051651901 R13: 0000000000000000 R14: ffff888115e

    • Auf 5.15.0-1043.49~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2023-53667

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

    net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize

    In the Linux kernel, the following vulnerability has been resolved: net: cdc_ncm: Deal with too low values of dwNtbOutMaxSize Currently in cdc_ncm_check_tx_max(), if dwNtbOutMaxSize is lower than the calculated "min" value, but greater than zero, the logic sets tx_max to dwNtbOutMaxSize. This is then used to allocate a new SKB in cdc_ncm_fill_tx_frame() where all the data is handled. For small values of dwNtbOutMaxSize the memory allocated during alloc_skb(dwNtbOutMaxSize, GFP_ATOMIC) will have the same size, due to how size is aligned at alloc time: size = SKB_DATA_ALIGN(size); size += SKB_DATA_ALIGN(sizeof(struct skb_shared_info

    • Auf 5.15.0-1040.46~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2023-53666

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

    ASoC: codecs: wcd938x: fix missing mbhc init error handling

    In the Linux kernel, the following vulnerability has been resolved: ASoC: codecs: wcd938x: fix missing mbhc init error handling MBHC initialisation can fail so add the missing error handling to avoid dereferencing an error pointer when later configuring the jack: Unable to handle kernel paging request at virtual address fffffffffffffff8 pc : wcd_mbhc_start+0x28/0x380 [snd_soc_wcd_mbhc] lr : wcd938x_codec_set_jack+0x28/0x48 [snd_soc_wcd938x] Call trace: wcd_mbhc_start+0x28/0x380 [snd_soc_wcd_mbhc] wcd938x_codec_set_jack+0x28/0x48 [snd_soc_wcd938x] snd_soc_component_set_jack+0x28/0x8c [snd_soc_core] qcom

    • Auf 5.15.0-1045.51~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2023-53661

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

    bnxt: avoid overflow in bnxt_get_nvram_directory()

    In the Linux kernel, the following vulnerability has been resolved: bnxt: avoid overflow in bnxt_get_nvram_directory() The value of an arithmetic expression is subject of possible overflow due to a failure to cast operands to a larger data type before performing arithmetic. Used macro for multiplication instead operator for avoiding overflow. Found by Security Code and Linux Verification Center (linuxtesting.org) with SVACE.

    • Auf 5.15.0-1040.46~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2023-53660

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

    bpf, cpumap: Handle skb as well when clean up ptr_ring

    In the Linux kernel, the following vulnerability has been resolved: bpf, cpumap: Handle skb as well when clean up ptr_ring The following warning was reported when running xdp_redirect_cpu with both skb-mode and stress-mode enabled: ------------[ cut here ]------------ Incorrect XDP memory type (-2128176192) usage WARNING: CPU: 7 PID: 1442 at net/core/xdp.c:405 Modules linked in: CPU: 7 PID: 1442 Comm: kworker/7:0 Tainted: G 6.5.0-rc2+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996) Workqueue: events __cpu_map_entry_free RIP: 0010:__xdp_return+0x1e4/0x4a0 ...... Call Trace: <TASK> ? show_regs+0x65/0x70

    • Auf 5.15.0-1045.51~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2023-53659

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

    iavf: Fix out-of-bounds when setting channels on remove

    In the Linux kernel, the following vulnerability has been resolved: iavf: Fix out-of-bounds when setting channels on remove If we set channels greater during iavf_remove(), and waiting reset done would be timeout, then returned with error but changed num_active_queues directly, that will lead to OOB like the following logs. Because the num_active_queues is greater than tx/rx_rings[] allocated actually. Reproducer: [root@host ~]# cat repro.sh #!/bin/bash pf_dbsf="0000:41:00.0" vf0_dbsf="0000:41:02.0" g_pids=() function do_set_numvf() { echo 2 >/sys/bus/pci/devices/${pf_dbsf}/sriov_numvfs sleep $((RANDOM%3+1))

    • Auf 5.15.0-1045.51~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 →