VYPR

rpm package

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

pkg:rpm/suse/kernel-docs&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Development%20Tools%2015%20SP7

Vulnerabilities (2,375)

  • CVE-2025-38724CriSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: nfsd: handle get_client_locked() failure in nfsd4_setclientid_confirm() Lei Lu recently reported that nfsd4_setclientid_confirm() did not check the return value from get_client_locked(). a SETCLIENTID_CONFIRM c

  • CVE-2025-38722HigSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: habanalabs: fix UAF in export_dmabuf() As soon as we'd inserted a file reference into descriptor table, another thread could close it. That's fine for the case when all we are doing is returning that descripto

  • CVE-2025-38721MedSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: netfilter: ctnetlink: fix refcount leak on table dump There is a reference count leak in ctnetlink_dump_table(): if (res < 0) { nf_conntrack_get(&ct->ct_general); // HERE c

  • CVE-2025-38718HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: sctp: linearize cloned gso packets in sctp_rcv A cloned head skb still shares these frag skbs in fraglist with the original head skb. It's not safe to access these frag skbs. syzbot reported two use-of-uniniti

  • CVE-2025-38715HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: hfs: fix slab-out-of-bounds in hfs_bnode_read() This patch introduces is_bnode_offset_valid() method that checks the requested offset value. Also, it introduces check_and_correct_requested_length() method that

  • CVE-2025-38714HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds in hfsplus_bnode_read() The hfsplus_bnode_read() method can trigger the issue: [ 174.852007][ T9784] ================================================================== [ 174.8

  • CVE-2025-38713HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: hfsplus: fix slab-out-of-bounds read in hfsplus_uni2asc() The hfsplus_readdir() method is capable to crash by calling hfsplus_uni2asc(): [ 667.121659][ T9805] =================================================

  • CVE-2025-38712MedSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: hfsplus: don't use BUG_ON() in hfsplus_create_attributes_file() When the volume header contains erroneous values that do not reflect the actual state of the filesystem, hfsplus_fill_super() assumes that the att

  • CVE-2025-38710HigSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: gfs2: Validate i_depth for exhash directories A fuzzer test introduced corruption that ends up with a depth of 0 in dir_e_read(), causing an undefined shift by 32 at: index = hash >> (32 - dip->i_depth); As

  • CVE-2025-38709MedSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: loop: Avoid updating block size under exclusive owner Syzbot came up with a reproducer where a loop device block size is changed underneath a mounted filesystem. This causes a mismatch between the block device

  • CVE-2025-38706MedSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: core: Check for rtd == NULL in snd_soc_remove_pcm_runtime() snd_soc_remove_pcm_runtime() might be called with rtd == NULL which will leads to null pointer dereference. This was reproduced with topology lo

  • CVE-2025-38705MedSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/pm: fix null pointer access Writing a string without delimiters (' ', '\n', '\0') to the under gpu_od/fan_ctrl sysfs or pp_power_profile_mode for the CUSTOM profile will result in a null pointer derefer

  • CVE-2025-38703HigSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: drm/xe: Make dma-fences compliant with the safe access rules Xe can free some of the data pointed to by the dma-fences it exports. Most notably the timeline name can get freed if userspace closes the associated

  • CVE-2025-38702HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: fbdev: fix potential buffer overflow in do_register_framebuffer() The current implementation may lead to buffer overflow when: 1. Unregistration creates NULL gaps in registered_fb[] 2. All array slots become

  • CVE-2025-38701MedSep 4, 2025
    affected < 6.4.0-150700.53.19.1fixed 6.4.0-150700.53.19.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: do not BUG when INLINE_DATA_FL lacks system.data xattr A syzbot fuzzed image triggered a BUG_ON in ext4_update_inline_data() when an inode had the INLINE_DATA_FL flag set but was missing the system.data e

  • CVE-2025-38700MedSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized

  • CVE-2025-38699HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: bfa: Double-free fix When the bfad_im_probe() function fails during initialization, the memory pointed to by bfad->im is freed without setting bfad->im to NULL. Subsequently, during driver uninstallation

  • CVE-2025-38698MedSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: jfs: Regular file corruption check The reproducer builds a corrupted file on disk with a negative i_size value. Add a check when opening this file to avoid subsequent operation failures.

  • CVE-2025-38697HigSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: jfs: upper bound check of tree index in dbAllocAG When computing the tree index in dbAllocAG, we never check if we are out of bounds realative to the size of the stree. This could happen in a scenario where the

  • CVE-2025-38695MedSep 4, 2025
    affected < 6.4.0-150700.53.22.1fixed 6.4.0-150700.53.22.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure If a call to lpfc_sli4_read_rev() from lpfc_sli4_hba_setup() fails, the resultant cleanup routine lpfc_sli4_vport_delete_fcp_xri_aborted

Page 68 of 119