p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in linux-lowlatency-hwe-5.15 · Seite 173

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 4513

  1. CVE-2023-52809

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

    scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup()

    In the Linux kernel, the following vulnerability has been resolved: scsi: libfc: Fix potential NULL pointer dereference in fc_lport_ptp_setup() fc_lport_ptp_setup() did not check the return value of fc_rport_create() which can return NULL and would cause a NULL pointer dereference. Address this issue by checking return value of fc_rport_create() and log error message on fc_rport_create() failed.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2023-52808

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

    scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs

    In the Linux kernel, the following vulnerability has been resolved: scsi: hisi_sas: Set debugfs_dir pointer to NULL after removing debugfs If init debugfs failed during device registration due to memory allocation failure, debugfs_remove_recursive() is called, after which debugfs_dir is not set to NULL. debugfs_remove_recursive() will be called again during device removal. As a result, illegal pointer is accessed. [ 1665.467244] hisi_sas_v3_hw 0000:b4:02.0: failed to init debugfs! ... [ 1669.836708] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0 [ 1669.872669] pc : down_write+0x24/0x70 [ 1669.876315] l

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2023-52806

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

    ALSA: hda: Fix possible null-ptr-deref when assigning a stream

    In the Linux kernel, the following vulnerability has been resolved: ALSA: hda: Fix possible null-ptr-deref when assigning a stream While AudioDSP drivers assign streams exclusively of HOST or LINK type, nothing blocks a user to attempt to assign a COUPLED stream. As supplied substream instance may be a stub, what is the case when code-loading, such scenario ends with null-ptr-deref.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2023-52805

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

    jfs: fix array-index-out-of-bounds in diAlloc

    In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in diAlloc Currently there is not check against the agno of the iag while allocating new inodes to avoid fragmentation problem. Added the check which is required.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2023-52804

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

    fs/jfs: Add validity check for db_maxag and db_agpref

    In the Linux kernel, the following vulnerability has been resolved: fs/jfs: Add validity check for db_maxag and db_agpref Both db_maxag and db_agpref are used as the index of the db_agfree array, but there is currently no validity check for db_maxag and db_agpref, which can lead to errors. The following is related bug reported by Syzbot: UBSAN: array-index-out-of-bounds in fs/jfs/jfs_dmap.c:639:20 index 7936 is out of range for type 'atomic_t[128]' Add checking that the values of db_maxag and db_agpref are valid indexes for the db_agfree array.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2023-52803

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

    SUNRPC: Fix RPC client cleaned up the freed pipefs dentries

    In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Fix RPC client cleaned up the freed pipefs dentries RPC client pipefs dentries cleanup is in separated rpc_remove_pipedir() workqueue,which takes care about pipefs superblock locking. In some special scenarios, when kernel frees the pipefs sb of the current client and immediately alloctes a new pipefs sb, rpc_remove_pipedir function would misjudge the existence of pipefs sb which is not the one it used to hold. As a result, the rpc_remove_pipedir would clean the released freed pipefs dentries. To fix this issue, rpc_remove_pipedir should check whether the current p

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  7. CVE-2023-52800

    Mittel · CVSS 4.4EPSS 0,23%Korrektur verfügbar

    wifi: ath11k: fix htt pktlog locking

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix htt pktlog locking The ath11k active pdevs are protected by RCU but the htt pktlog handling code calling ath11k_mac_get_ar_by_pdev_id() was not marked as a read-side critical section. Mark the code in question as an RCU read-side critical section to avoid any potential use-after-free issues. Compile tested only.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  8. CVE-2023-52799

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

    jfs: fix array-index-out-of-bounds in dbFindLeaf

    In the Linux kernel, the following vulnerability has been resolved: jfs: fix array-index-out-of-bounds in dbFindLeaf Currently while searching for dmtree_t for sufficient free blocks there is an array out of bounds while getting element in tp->dm_stree. To add the required check for out of bound we first need to determine the type of dmtree. Thus added an extra parameter to dbFindLeaf so that the type of tree can be determined and the required check can be applied.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  9. CVE-2023-52798

    Hoch · CVSS 8.8EPSS 1,03%Korrektur verfügbar

    wifi: ath11k: fix dfs radar event locking

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: fix dfs radar event locking The ath11k active pdevs are protected by RCU but the DFS radar event handling code calling ath11k_mac_get_ar_by_pdev_id() was not marked as a read-side critical section. Mark the code in question as an RCU read-side critical section to avoid any potential use-after-free issues. Compile tested only.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  10. CVE-2023-52796

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

    ipvlan: add ipvlan_route_v6_outbound() helper

    In the Linux kernel, the following vulnerability has been resolved: ipvlan: add ipvlan_route_v6_outbound() helper Inspired by syzbot reports using a stack of multiple ipvlan devices. Reduce stack size needed in ipvlan_process_v6_outbound() by moving the flowi6 struct used for the route lookup in an non inlined helper. ipvlan_route_v6_outbound() needs 120 bytes on the stack, immediately reclaimed. Also make sure ipvlan_process_v4_outbound() is not inlined. We might also have to lower MAX_NEST_DEV, because only syzbot uses setups with more than four stacked devices. BUG: TASK stack guard page was hit at ffffc9000e803ff8 (stack is ffffc900

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  11. CVE-2023-52791

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

    i2c: core: Run atomic i2c xfer when !preemptible

    In the Linux kernel, the following vulnerability has been resolved: i2c: core: Run atomic i2c xfer when !preemptible Since bae1d3a05a8b, i2c transfers are non-atomic if preemption is disabled. However, non-atomic i2c transfers require preemption (e.g. in wait_for_completion() while waiting for the DMA). panic() calls preempt_disable_notrace() before calling emergency_restart(). Therefore, if an i2c device is used for the restart, the xfer should be atomic. This avoids warnings like: [ 12.667612] WARNING: CPU: 1 PID: 1 at kernel/rcu/tree_plugin.h:318 rcu_note_context_switch+0x33c/0x6b0 [ 12.676926] Voluntary context switch within RCU r

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  12. CVE-2023-52789

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

    tty: vcc: Add check for kstrdup() in vcc_probe()

    In the Linux kernel, the following vulnerability has been resolved: tty: vcc: Add check for kstrdup() in vcc_probe() Add check for the return value of kstrdup() and return the error, if it fails in order to avoid NULL pointer dereference.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  13. CVE-2023-52788

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

    i915/perf: Fix NULL deref bugs with drm_dbg() calls

    In the Linux kernel, the following vulnerability has been resolved: i915/perf: Fix NULL deref bugs with drm_dbg() calls When i915 perf interface is not available dereferencing it will lead to NULL dereferences. As returning -ENOTSUPP is pretty clear return when perf interface is not available. [tursulin: added stable tag] (cherry picked from commit 36f27350ff745bd228ab04d7845dfbffc177a889)

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  14. CVE-2023-52784

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

    bonding: stop the device in bond_setup_by_slave()

    In the Linux kernel, the following vulnerability has been resolved: bonding: stop the device in bond_setup_by_slave() Commit 9eed321cde22 ("net: lapbether: only support ethernet devices") has been able to keep syzbot away from net/lapb, until today. In the following splat [1], the issue is that a lapbether device has been created on a bonding device without members. Then adding a non ARPHRD_ETHER member forced the bonding master to change its type. The fix is to make sure we call dev_close() in bond_setup_by_slave() so that the potential linked lapbether devices (or any other devices having assumptions on the physical device) are removed.

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  15. CVE-2023-52781

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

    usb: config: fix iteration issue in 'usb_get_bos_descriptor()'

    In the Linux kernel, the following vulnerability has been resolved: usb: config: fix iteration issue in 'usb_get_bos_descriptor()' The BOS descriptor defines a root descriptor and is the base descriptor for accessing a family of related descriptors. Function 'usb_get_bos_descriptor()' encounters an iteration issue when skipping the 'USB_DT_DEVICE_CAPABILITY' descriptor type. This results in the same descriptor being read repeatedly. To address this issue, a 'goto' statement is introduced to ensure that the pointer and the amount read is updated correctly. This ensures that the function iterates to the next descriptor instead of reading th

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  16. CVE-2023-52775

    Hoch · CVSS 8.2EPSS 0,67%Korrektur verfügbar

    net/smc: avoid data corruption caused by decline

    In the Linux kernel, the following vulnerability has been resolved: net/smc: avoid data corruption caused by decline We found a data corruption issue during testing of SMC-R on Redis applications. The benchmark has a low probability of reporting a strange error as shown below. "Error: Protocol error, got "\xe2" as reply type byte" Finally, we found that the retrieved error data was as follows: 0xE2 0xD4 0xC3 0xD9 0x04 0x00 0x2C 0x20 0xA6 0x56 0x00 0x16 0x3E 0x0C 0xCB 0x04 0x02 0x01 0x00 0x00 0x20 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0xE2 It is quite obvious that this is a SMC DECLINE mess

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  17. CVE-2023-52774

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

    s390/dasd: protect device queue against concurrent access

    In the Linux kernel, the following vulnerability has been resolved: s390/dasd: protect device queue against concurrent access In dasd_profile_start() the amount of requests on the device queue are counted. The access to the device queue is unprotected against concurrent access. With a lot of parallel I/O, especially with alias devices enabled, the device queue can change while dasd_profile_start() is accessing the queue. In the worst case this leads to a kernel panic due to incorrect pointer accesses. Fix this by taking the device lock before accessing the queue and counting the requests. Additionally the check for a valid profile data poi

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  18. CVE-2023-52772

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

    af_unix: fix use-after-free in unix_stream_read_actor()

    In the Linux kernel, the following vulnerability has been resolved: af_unix: fix use-after-free in unix_stream_read_actor() syzbot reported the following crash [1] After releasing unix socket lock, u->oob_skb can be changed by another thread. We must temporarily increase skb refcount to make sure this other thread will not free the skb under us. [1] BUG: KASAN: slab-use-after-free in unix_stream_read_actor+0xa7/0xc0 net/unix/af_unix.c:2866 Read of size 4 at addr ffff88801f3b9cc4 by task syz-executor107/5297 CPU: 1 PID: 5297 Comm: syz-executor107 Not tainted 6.6.0-syzkaller-15910-gb8e3a87a627b #0 Hardware name: Google Google Compute Engi

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  19. CVE-2023-52768

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

    wifi: wilc1000: use vmm_table as array in wilc struct

    In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: use vmm_table as array in wilc struct Enabling KASAN and running some iperf tests raises some memory issues with vmm_table: BUG: KASAN: slab-out-of-bounds in wilc_wlan_handle_txq+0x6ac/0xdb4 Write of size 4 at addr c3a61540 by task wlan0-tx/95 KASAN detects that we are writing data beyond range allocated to vmm_table. There is indeed a mismatch between the size passed to allocator in wilc_wlan_init, and the range of possible indexes used later: allocation size is missing a multiplication by sizeof(u32)

    • Auf 5.15.0-100.110~20.04.1 aktualisieren
    Veröffentlicht Aktualisiert
  20. CVE-2023-52766

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

    i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler

    In the Linux kernel, the following vulnerability has been resolved: i3c: mipi-i3c-hci: Fix out of bounds access in hci_dma_irq_handler Do not loop over ring headers in hci_dma_irq_handler() that are not allocated and enabled in hci_dma_init(). Otherwise out of bounds access will occur from rings->headers[i] access when i >= number of allocated ring headers.

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