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,117)

  • CVE-2025-37819HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: irqchip/gic-v2m: Prevent use after free of gicv2m_get_fwnode() With ACPI in place, gicv2m_get_fwnode() is registered with the pci subsystem as pci_msi_get_fwnode_cb(), which may get invoked at runtime during a

  • CVE-2025-37816MedMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: mei: vsc: Fix fortify-panic caused by invalid counted_by() use gcc 15 honors the __counted_by(len) attribute on vsc_tp_packet.buf[] and the vsc-tp.c code is using this in a wrong way. len does not contain the a

  • CVE-2025-37815MedMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: misc: microchip: pci1xxxx: Fix Kernel panic during IRQ handler registration Resolve kernel panic while accessing IRQ handler associated with the generated IRQ. This is done by acquiring the spinlock and storing

  • CVE-2025-37814HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: tty: Require CAP_SYS_ADMIN for all usages of TIOCL_SELMOUSEREPORT This requirement was overeagerly loosened in commit 2f83e38a095f ("tty: Permit some TIOCL_SETSEL modes without CAP_SYS_ADMIN"), but as it turns

  • CVE-2025-37813HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: usb: xhci: Fix invalid pointer dereference in Etron workaround This check is performed before prepare_transfer() and prepare_ring(), so enqueue can already point at the final link TRB of a segment. And indeed i

  • CVE-2025-37812MedMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: usb: cdns3: Fix deadlock when using NCM gadget The cdns3 driver has the same NCM deadlock as fixed in cdnsp by commit 58f2fcb3a845 ("usb: cdnsp: Fix deadlock issue during using NCM gadget"). Under PREEMPT_RT t

  • CVE-2025-37811MedMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: usb: chipidea: ci_hdrc_imx: fix usbmisc handling usbmisc is an optional device property so it is totally valid for the corresponding data->usbmisc_data to have a NULL value. Check that before dereferencing the

  • CVE-2025-37810HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: gadget: check that event count does not exceed event buffer length The event count is read from register DWC3_GEVNTCOUNT. There is a check for the count being zero, but not for exceeding the event bu

  • CVE-2025-37809MedMay 8, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: usb: typec: class: Fix NULL pointer access Concurrent calls to typec_partner_unlink_device can lead to a NULL pointer dereference. This patch adds a mutex to protect USB device pointers and prevent this issue.

  • CVE-2025-37805MedMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: sound/virtio: Fix cancel_sync warnings on uninitialized work_structs Betty reported hitting the following warning: [ 8.709131][ T221] WARNING: CPU: 2 PID: 221 at kernel/workqueue.c:4182 ... [ 8.713282][

  • CVE-2025-37803HigMay 8, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: udmabuf: fix a buf size overflow issue during udmabuf creation by casting size_limit_mb to u64 when calculate pglimit.

  • CVE-2025-37801HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: spi: spi-imx: Add check for spi_imx_setupxfer() Add check for the return value of spi_imx_setupxfer(). spi_imx->rx and spi_imx->tx function pointer can be NULL when spi_imx_setupxfer() return error, and make NU

  • CVE-2025-37800HigMay 8, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: driver core: fix potential NULL pointer dereference in dev_uevent() If userspace reads "uevent" device attribute at the same time as another threads unbinds the device from its driver, change to dev->driver fro

  • CVE-2024-58237HigMay 5, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: bpf: consider that tail calls invalidate packet pointers Tail-called programs could execute any of the helpers that invalidate packet pointers. Hence, conservatively assume that each tail call invalidates packe

  • CVE-2024-58100HigMay 5, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: bpf: check changes_pkt_data property for extension programs When processing calls to global sub-programs, verifier decides whether to invalidate all packet pointers in current state depending on the changes_pkt

  • CVE-2024-58098HigMay 5, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: bpf: track changes_pkt_data property for global functions When processing calls to certain helpers, verifier invalidates all packet pointers in a current state. For example, consider the following program:

  • CVE-2025-37799HigMay 3, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: vmxnet3: Fix malformed packet sizing in vmxnet3_process_xdp vmxnet3 driver's XDP handling is buggy for packet sizes using ring0 (that is, packet sizes between 128 - 3k bytes). We noticed MTU-related connectivi

  • CVE-2025-37798HigMay 2, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: codel: remove sch->q.qlen check before qdisc_tree_reduce_backlog() After making all ->qlen_notify() callbacks idempotent, now it is safe to remove the check of qlen!=0 from both fq_codel_dequeue() and codel_qdi

  • CVE-2025-37797HigMay 2, 2025
    affected < 6.4.0-150700.20.3.1fixed 6.4.0-150700.20.3.1

    In the Linux kernel, the following vulnerability has been resolved: net_sched: hfsc: Fix a UAF vulnerability in class handling This patch fixes a Use-After-Free vulnerability in the HFSC qdisc class handling. The issue occurs due to a time-of-check/time-of-use condition in hfsc

  • CVE-2025-37796HigMay 1, 2025
    affected < 6.4.0-150700.20.6.1fixed 6.4.0-150700.20.6.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: at76c50x: fix use after free access in at76_disconnect The memory pointed to by priv is freed at the end of at76_delete_device function (using ieee80211_free_hw). But the code then accesses the udev field

Page 84 of 106