suse/kernel-docs&distro=SUSE Linux Enterprise Module for Development Tools 15 SP5

Vulnerabilities (2,437)

• CVE-2024-27079MedMay 1, 2024
  affected < 5.14.21-150500.55.80.2fixed 5.14.21-150500.55.80.2

  In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Fix NULL domain on device release In the kdump kernel, the IOMMU operates in deferred_attach mode. In this mode, info->domain may not yet be assigned by the time the release_device function is calle

• CVE-2024-27078MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: v4l2-tpg: fix some memleaks in tpg_alloc In tpg_alloc, resources should be deallocated in each and every error-handling paths, since they are allocated in for statements. Otherwise there would be memleak

• CVE-2024-27077MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: v4l2-mem2mem: fix a memleak in v4l2_m2m_register_entity The entity->name (i.e. name) is allocated in v4l2_m2m_register_entity but isn't freed in its following error-handling paths. This patch adds such d

• CVE-2024-27076MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: imx: csc/scaler: fix v4l2_ctrl_handler memory leak Free the memory allocated in v4l2_ctrl_handler_init on release.

• CVE-2024-27075HigMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: dvb-frontends: avoid stack overflow warnings with clang A previous patch worked around a KASAN issue in stv0367, now a similar problem showed up with clang: drivers/media/dvb-frontends/stv0367.c:1222:12

• CVE-2024-27074MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: go7007: fix a memleak in go7007_load_encoder In go7007_load_encoder, bounce(i.e. go->boot_fw), is allocated without a deallocation thereafter. After the following call chain: saa7134_go7007_init |-> g

• CVE-2024-27073MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: ttpci: fix two memleaks in budget_av_attach When saa7146_register_device and saa7146_vv_init fails, budget_av_attach should free the resources it allocates, like the error-handling of ttpci_budget_init d

• CVE-2024-27072MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: media: usbtv: Remove useless locks in usbtv_video_free() Remove locks calls in usbtv_video_free() because are useless and may led to a deadlock as reported here: https://syzkaller.appspot.com/x/bisect.txt?x=166

• CVE-2024-27065HigMay 1, 2024
  affected < 5.14.21-150500.55.73.2fixed 5.14.21-150500.55.73.2

  In the Linux kernel, the following vulnerability has been resolved: netfilter: nf_tables: do not compare internal table flags on updates Restore skipping transaction if table update does not modify flags.

• CVE-2024-27062MedMay 1, 2024
  affected < 5.14.21-150500.55.62.2fixed 5.14.21-150500.55.62.2

  In the Linux kernel, the following vulnerability has been resolved: nouveau: lock the client object tree. It appears the client object tree has no locking unless I've missed something else. Fix races around adding/removing client objects, mostly vram bar mappings. 4562.099306

• CVE-2024-27059MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: USB: usb-storage: Prevent divide-by-0 error in isd200_ata_command The isd200 sub-driver in usb-storage uses the HEADS and SECTORS values in the ATA ID information to calculate cylinder and head values when crea

• CVE-2024-27056MedMay 1, 2024
  affected < 5.14.21-150500.55.62.2fixed 5.14.21-150500.55.62.2

  In the Linux kernel, the following vulnerability has been resolved: wifi: iwlwifi: mvm: ensure offloading TID queue exists The resume code path assumes that the TX queue for the offloading TID has been configured. At resume time it then tries to sync the write pointer as it may

• CVE-2024-27054MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix double module refcount decrement Once the discipline is associated with the device, deleting the device takes care of decrementing the module's refcount. Doing it manually on this error path cau

• CVE-2024-27053CriMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: wifi: wilc1000: fix RCU usage in connect path With lockdep enabled, calls to the connect function from cfg802.11 layer lead to the following warning: ============================= WARNING: suspicious RCU usage

• CVE-2024-27052HigMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: wifi: rtl8xxxu: add cancel_work_sync() for c2hcmd_work The workqueue might still be running, when the driver is stopped. To avoid a use-after-free, call cancel_work_sync() in rtl8xxxu_stop().

• CVE-2024-27051MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: cpufreq: brcmstb-avs-cpufreq: add check for cpufreq_cpu_get's return value cpufreq_cpu_get may return NULL. To avoid NULL-dereference check it and return 0 in case of error. Found by Linux Verification Center

• CVE-2024-27047MedMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: net: phy: fix phy_get_internal_delay accessing an empty array The phy_get_internal_delay function could try to access to an empty array in the case that the driver is calling phy_get_internal_delay without defi

• CVE-2024-27046MedMay 1, 2024
  affected < 5.14.21-150500.55.62.2fixed 5.14.21-150500.55.62.2

  In the Linux kernel, the following vulnerability has been resolved: nfp: flower: handle acti_netdevs allocation failure The kmalloc_array() in nfp_fl_lag_do_work() will return null, if the physical memory has run out. As a result, if we dereference the acti_netdevs, the null po

• CVE-2024-27045HigMay 1, 2024
  affected < 5.14.21-150500.55.68.1fixed 5.14.21-150500.55.68.1

  In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Fix a potential buffer overflow in 'dp_dsc_clock_en_read()' Tell snprintf() to store at most 10 bytes in the output buffer instead of 30. Fixes the below: drivers/gpu/drm/amd/amdgpu/../display

• CVE-2024-27043HigMay 1, 2024
  affected < 5.14.21-150500.55.62.2fixed 5.14.21-150500.55.62.2

  In the Linux kernel, the following vulnerability has been resolved: media: edia: dvbdev: fix a use-after-free In dvb_register_device, *pdvbdev is set equal to dvbdev, which is freed in several error-handling paths. However, *pdvbdev is not set to NULL after dvbdev's deallocatio