VYPR

rpm package

suse/kernel-docs&distro=SUSE Linux Enterprise Server for SAP Applications 15 SP4

pkg:rpm/suse/kernel-docs&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2015%20SP4

Vulnerabilities (2,843)

  • CVE-2023-53608HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix potential UAF of struct nilfs_sc_info in nilfs_segctor_thread() The finalization of nilfs_segctor_thread() can race with nilfs_segctor_kill_thread() which terminates that thread, potentially causing

  • CVE-2023-53607MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: ymfpci: Fix BUG_ON in probe function The snd_dma_buffer.bytes field now contains the aligned size, which this snd_BUG_ON() did not account for, resulting in the following: [ 9.625915] ------------[ cu

  • CVE-2023-53605MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: drm: amd: display: Fix memory leakage This commit fixes memory leakage in dc_construct_ctx() function.

  • CVE-2023-53604HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: dm integrity: call kmem_cache_destroy() in dm_integrity_init() error path Otherwise the journal_io_cache will leak if dm_register_target() fails.

  • CVE-2023-53603MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Avoid fcport pointer dereference Klocwork reported warning of NULL pointer may be dereferenced. The routine exits when sa_ctl is NULL and fcport is allocated after the exit call thus causing NUL

  • CVE-2023-53597HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: cifs: fix mid leak during reconnection after timeout threshold When the number of responses with status of STATUS_IO_TIMEOUT exceeds a specified threshold (NUM_STATUS_IO_TIMEOUT), we reconnect the connection. B

  • CVE-2023-53594MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: driver core: fix resource leak in device_add() When calling kobject_add() failed in device_add(), it will call cleanup_glue_dir() to free resource. But in kobject_add(), dev->kobj.parent has been set to NULL. T

  • CVE-2023-53592MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: gpio: sifive: Fix refcount leak in sifive_gpio_probe of_irq_find_parent() returns a node pointer with refcount incremented, We should use of_node_put() on it when not needed anymore. Add missing of_node_put() t

  • CVE-2023-53589HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: don't trust firmware n_channels If the firmware sends us a corrupted MCC response with n_channels much larger than the command response can be, we might copy far too much (uninitialized) mem

  • CVE-2023-53587HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: ring-buffer: Sync IRQ works before buffer destruction If something was written to the buffer just before destruction, it may be possible (maybe not in a real system, but it did happen in ARCH=um with time-trave

  • CVE-2023-53582MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: brcmfmac: ensure CLM version is null-terminated to prevent stack-out-of-bounds Fix a stack-out-of-bounds read in brcmfmac that occurs when 'buf' that is not null-terminated is passed as an argument of str

  • CVE-2023-53579MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: gpio: mvebu: fix irq domain leak Uwe Kleine-König pointed out we still have one resource leak in the mvebu driver triggered on driver detach. Let's address it with a custom devm action.

  • CVE-2023-53576MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: null_blk: Always check queue mode setting from configfs Make sure to check device queue mode in the null_validate_conf() and return error for NULL_Q_RQ as we don't allow legacy I/O path, without this patch we g

  • CVE-2023-53574MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: rtw88: delete timer and free skb queue when unloading Fix possible crash and memory leak on driver unload by deleting TX purge timer and freeing C2H queue in 'rtw_core_deinit()', shrink critical section i

  • CVE-2023-53572HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: clk: imx: scu: use _safe list iterator to avoid a use after free This loop is freeing "clk" so it needs to use list_for_each_entry_safe(). Otherwise it dereferences a freed variable to get the next item on the

  • CVE-2023-53571MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: drm/i915: Make intel_get_crtc_new_encoder() less oopsy The point of the WARN was to print something, not oops straight up. Currently that is precisely what happens if we can't find the connector for the crtc in

  • CVE-2023-53568MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: don't leak memory if dev_set_name() fails When dev_set_name() fails, zcdn_create() doesn't free the newly allocated resources. Do it.

  • CVE-2023-53567MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: spi: qup: Don't skip cleanup in remove's error path Returning early in a platform driver's remove callback is wrong. In this case the dma resources are not released in the error path. this is never retried late

  • CVE-2023-53566HigOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_set_rbtree: fix null deref on element insertion There is no guarantee that rb_prev() will not return NULL in nft_rbtree_gc_elem(): general protection fault, probably for non-canonical address 0x

  • CVE-2023-53564MedOct 4, 2025
    affected < 5.14.21-150400.24.184.1fixed 5.14.21-150400.24.184.1

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix defrag path triggering jbd2 ASSERT code path: ocfs2_ioctl_move_extents ocfs2_move_extents ocfs2_defrag_extent __ocfs2_move_extent + ocfs2_journal_access_di + ocfs2_split_extent //sub-

Page 25 of 143