VYPR

rpm package

suse/kernel-source-rt&distro=SUSE Real Time Module 15 SP5

pkg:rpm/suse/kernel-source-rt&distro=SUSE%20Real%20Time%20Module%2015%20SP5

Vulnerabilities (2,442)

  • CVE-2024-35961MedMay 20, 2024
    affected < 5.14.21-150500.13.64.1fixed 5.14.21-150500.13.64.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Register devlink first under devlink lock In case device is having a non fatal FW error during probe, the driver will report the error to user via devlink. This will trigger a WARN_ON, since mlx5 is c

  • CVE-2024-35960CriMay 20, 2024
    affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5: Properly link new fs rules into the tree Previously, add_rule_fg would only add newly created rules from the handle into the tree when they had a refcount of 1. On the other hand, create_flow_handle t

  • CVE-2024-35959MedMay 20, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: net/mlx5e: Fix mlx5e_priv_init() cleanup flow When mlx5e_priv_init() fails, the cleanup flow calls mlx5e_selq_cleanup which calls mlx5e_selq_apply() that assures that the `priv->state_lock` is held using lockde

  • CVE-2024-35958MedMay 20, 2024
    affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1

    In the Linux kernel, the following vulnerability has been resolved: net: ena: Fix incorrect descriptor free behavior ENA has two types of TX queues: - queues which only process TX packets arriving from the network stack - queues which only process TX packets forwarded to it by

  • CVE-2024-35956MedMay 20, 2024
    affected < 5.14.21-150500.13.61.1fixed 5.14.21-150500.13.61.1

    In the Linux kernel, the following vulnerability has been resolved: btrfs: qgroup: fix qgroup prealloc rsv leak in subvolume operations Create subvolume, create snapshot and delete subvolume all use btrfs_subvolume_reserve_metadata() to reserve metadata for the changes done to

  • CVE-2024-35955HigMay 20, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: kprobes: Fix possible use-after-free issue on kprobe registration When unloading a module, its state is changing MODULE_STATE_LIVE -> MODULE_STATE_GOING -> MODULE_STATE_UNFORMED. Each change will take a time.

  • CVE-2024-35952MedMay 20, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: drm/ast: Fix soft lockup There is a while-loop in ast_dp_set_on_off() that could lead to infinite-loop. This is because the register, VGACRI-Dx, checked in this API is a scratch register actually controlled by

  • CVE-2024-35951MedMay 20, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() Subject: [PATCH] drm/panfrost: Fix the error path in panfrost_mmu_map_fault_addr() If some the pages or sgt allocation failed, we shouldn't re

  • CVE-2024-35950MedMay 20, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: drm/client: Fully protect modes[] with dev->mode_config.mutex The modes[] array contains pointers to modes on the connectors' mode lists, which are protected by dev->mode_config.mutex. Thus we need to extend mo

  • CVE-2024-35949HigMay 20, 2024
    affected < 5.14.21-150500.13.64.1fixed 5.14.21-150500.13.64.1

    In the Linux kernel, the following vulnerability has been resolved: btrfs: make sure that WRITTEN is set on all metadata blocks We previously would call btrfs_check_leaf() if we had the check integrity code enabled, which meant that we could only run the extended leaf checks if

  • CVE-2024-35947MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: dyndbg: fix old BUG_ON in >control parser Fix a BUG_ON from 2009. Even if it looks "unreachable" (I didn't really look), lets make sure by removing it, doing pr_err and return -EINVAL instead.

  • CVE-2024-35945MedMay 19, 2024
    affected < 5.14.21-150500.13.67.3fixed 5.14.21-150500.13.67.3

    In the Linux kernel, the following vulnerability has been resolved: net: phy: phy_device: Prevent nullptr exceptions on ISR If phydev->irq is set unconditionally, check for valid interrupt handler or fall back to polling mode to prevent nullptr exceptions in interrupt service r

  • CVE-2024-35944MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: VMCI: Fix memcpy() run-time warning in dg_dispatch_as_host() Syzkaller hit 'WARNING in dg_dispatch_as_host' bug. memcpy: detected field-spanning write (size 56) of single field "&dg_info->msg" at drivers/misc/

  • CVE-2024-35943MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: pmdomain: ti: Add a null pointer check to the omap_prm_domain_init devm_kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by chec

  • CVE-2024-35940MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: pstore/zone: Add a null pointer check to the psz_kmsg_read kasprintf() returns a pointer to dynamically allocated memory which can be NULL upon failure. Ensure the allocation was successful by checking the poin

  • CVE-2024-35939HigMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: dma-direct: Leak pages on dma_set_decrypted() failure On TDX it is possible for the untrusted host to cause set_memory_encrypted() or set_memory_decrypted() to fail such that an error is returned and the result

  • CVE-2024-35938MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath11k: decrease MHI channel buffer length to 8KB Currently buf_len field of ath11k_mhi_config_qca6390 is assigned with 0, making MHI use a default size, 64KB, to allocate channel buffers. This is likely

  • CVE-2024-35937HigMay 19, 2024
    affected < 5.14.21-150500.13.79.1fixed 5.14.21-150500.13.79.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: check A-MSDU format more carefully If it looks like there's another subframe in the A-MSDU but the header isn't fully there, we can end up reading data out of bounds, only to discard later. Make

  • CVE-2024-35936MedMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: btrfs: handle chunk tree lookup error in btrfs_relocate_sys_chunks() The unhandled case in btrfs_relocate_sys_chunks() loop is a corruption, as it could be caused only by two impossible conditions: - at first

  • CVE-2024-35935LowMay 19, 2024
    affected < 5.14.21-150500.13.58.1fixed 5.14.21-150500.13.58.1

    In the Linux kernel, the following vulnerability has been resolved: btrfs: send: handle path ref underflow in header iterate_inode_ref() Change BUG_ON to proper error handling if building the path buffer fails. The pointers are not printed so we don't accidentally leak kernel a

Page 78 of 123