suse/kernel-obs-build&distro=SUSE Linux Enterprise High Performance Computing 15 SP4-ESPOS

Vulnerabilities (2,830)

• CVE-2023-53662Oct 7, 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: ext4: fix memory leaks in ext4_fname_{setup_filename,prepare_lookup} If the filename casefolding fails, we'll be leaking memory from the fscrypt_name struct, namely from the 'crypto_buf.name' member. Make sure

• CVE-2023-53659Oct 7, 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: 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,

• CVE-2023-53658Oct 7, 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: bcm-qspi: return error if neither hif_mspi nor mspi is available If neither a "hif_mspi" nor "mspi" resource is present, the driver will just early exit in probe but still return success. Apart from not do

• CVE-2022-50553Oct 7, 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: tracing/hist: Fix out-of-bound write on 'action_data.var_ref_idx' When generate a synthetic event with many params and then create a trace action for it [1], kernel panic happened [2]. It is because that in tr

• CVE-2022-50551Oct 7, 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: Fix potential shift-out-of-bounds in brcmf_fw_alloc_request() This patch fixes a shift-out-of-bounds in brcmfmac that occurs in BIT(chiprev) when a 'chiprev' provided by the device is too large.

• CVE-2022-50549Oct 7, 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 thin: Fix ABBA deadlock between shrink_slab and dm_pool_abort_metadata Following concurrent processes: P1(drop cache) P2(kworker) drop_caches_sysctl_handler drop_slab shrink_slab

• CVE-2022-50546Oct 7, 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: ext4: fix uninititialized value in 'ext4_evict_inode' Syzbot found the following issue: ===================================================== BUG: KMSAN: uninit-value in ext4_evict_inode+0xdd/0x26b0 fs/ext4/ino

• CVE-2022-50545Oct 7, 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: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemleak: unreferenced object 0xffff888116111000 (size 2048): comm "modprobe", pid 817, jiffies 4294759745 (age 76.502s) he

• CVE-2022-50544Oct 7, 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: usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info() xhci_alloc_stream_info() allocates stream context array for stream_info ->stream_ctx_array with xhci_alloc_stream_ctx(). When some error oc

• CVE-2022-50542Oct 7, 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: media: si470x: Fix use-after-free in si470x_int_in_callback() syzbot reported use-after-free in si470x_int_in_callback() [1]. This indicates that urb->context, which contains struct si470x_device object, is fr

• CVE-2022-50541Oct 7, 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: dmaengine: ti: k3-udma: Reset UDMA_CHAN_RT byte counters to prevent overflow UDMA_CHAN_RT_*BCNT_REG stores the real-time channel bytecount statistics. These registers are 32-bit hardware counters and the driver

• CVE-2022-50537Oct 7, 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: firmware: raspberrypi: fix possible memory leak in rpi_firmware_probe() In rpi_firmware_probe(), if mbox_request_channel() fails, the 'fw' will not be freed through rpi_firmware_delete(), fix this leak by calli

• CVE-2022-50535Oct 7, 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 potential null-deref in dm_resume [Why] Fixing smatch error: dm_resume() error: we previously assumed 'aconnector->dc_link' could be null [How] Check if dc_link null at the beginning of th

• CVE-2023-53651Oct 7, 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: Input: exc3000 - properly stop timer on shutdown We need to stop the timer on driver unbind or probe failures, otherwise we get UAF/Oops.

• CVE-2023-53650Oct 7, 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: fbdev: omapfb: lcd_mipid: Fix an error handling path in mipid_spi_probe() If 'mipid_detect()' fails, we must free 'md' to avoid a memory leak.

• CVE-2023-53648Oct 7, 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: ac97: Fix possible NULL dereference in snd_ac97_mixer smatch error: sound/pci/ac97/ac97_codec.c:2354 snd_ac97_mixer() error: we previously assumed 'rac97' could be null (see line 2072) remove redundant a

• CVE-2023-53644Oct 7, 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: media: radio-shark: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the radio-shark2 driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU

• CVE-2023-53641Oct 7, 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: ath9k: hif_usb: fix memory leak of remain_skbs hif_dev->remain_skb is allocated and used exclusively in ath9k_hif_usb_rx_stream(). It is implied that an allocated remain_skb is processed and subsequently

• CVE-2023-53640Oct 7, 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: ASoC: lpass: Fix for KASAN use_after_free out of bounds When we run syzkaller we get below Out of Bounds error. "KASAN: slab-out-of-bounds Read in regcache_flat_read" Below is the backtrace of the issue: BUG

• CVE-2023-53639Oct 7, 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: ath6kl: reduce WARN to dev_dbg() in callback The warn is triggered on a known race condition, documented in the code above the test, that is correctly handled. Using WARN() hinders automated testing. Red