VYPR

rpm package

suse/kernel-syms-azure&distro=SUSE Linux Enterprise Module for Public Cloud 15 SP7

pkg:rpm/suse/kernel-syms-azure&distro=SUSE%20Linux%20Enterprise%20Module%20for%20Public%20Cloud%2015%20SP7

Vulnerabilities (2,127)

  • CVE-2025-38730HigSep 4, 2025
    affected < 6.4.0-150700.20.15.1fixed 6.4.0-150700.20.15.1

    In the Linux kernel, the following vulnerability has been resolved: io_uring/net: commit partial buffers on retry Ring provided buffers are potentially only valid within the single execution context in which they were acquired. io_uring deals with this and invalidates them on r

  • CVE-2025-38729HigSep 4, 2025
    affected < 6.4.0-150700.20.18.1fixed 6.4.0-150700.20.18.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: usb-audio: Validate UAC3 power domain descriptors, too UAC3 power domain descriptors need to be verified with its variable bLength for avoiding the unexpected OOB accesses by malicious firmware, too.

  • CVE-2025-38728CriSep 4, 2025
    affected < 6.4.0-150700.20.24.1fixed 6.4.0-150700.20.24.1

    In the Linux kernel, the following vulnerability has been resolved: smb3: fix for slab out of bounds on mount to ksmbd With KASAN enabled, it is possible to get a slab out of bounds during mount to ksmbd due to missing check in parse_server_interfaces() (see below): BUG: KASA

  • CVE-2025-38727MedSep 4, 2025
    affected < 6.4.0-150700.20.18.1fixed 6.4.0-150700.20.18.1

    In the Linux kernel, the following vulnerability has been resolved: netlink: avoid infinite retry looping in netlink_unicast() netlink_attachskb() checks for the socket's read memory allocation constraints. Firstly, it has: rmem < READ_ONCE(sk->sk_rcvbuf) to check if the ju

  • CVE-2025-38725MedSep 4, 2025
    affected < 6.4.0-150700.20.18.1fixed 6.4.0-150700.20.18.1

    In the Linux kernel, the following vulnerability has been resolved: net: usb: asix_devices: add phy_mask for ax88772 mdio bus Without setting phy_mask for ax88772 mdio bus, current driver may create at most 32 mdio phy devices with phy address range from 0x00 ~ 0x1f. DLink DUB-

  • CVE-2025-38724CriSep 4, 2025
    affected < 6.4.0-150700.20.18.1fixed 6.4.0-150700.20.18.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.20.15.1fixed 6.4.0-150700.20.15.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.20.15.1fixed 6.4.0-150700.20.15.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.20.18.1fixed 6.4.0-150700.20.18.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.20.18.1fixed 6.4.0-150700.20.18.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.20.18.1fixed 6.4.0-150700.20.18.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.20.18.1fixed 6.4.0-150700.20.18.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.20.18.1fixed 6.4.0-150700.20.18.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.20.15.1fixed 6.4.0-150700.20.15.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.20.15.1fixed 6.4.0-150700.20.15.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.20.18.1fixed 6.4.0-150700.20.18.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.20.15.1fixed 6.4.0-150700.20.15.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.20.15.1fixed 6.4.0-150700.20.15.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.20.18.1fixed 6.4.0-150700.20.18.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.20.15.1fixed 6.4.0-150700.20.15.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

Page 55 of 107