VYPR

rpm package

opensuse/kernel-syms&distro=openSUSE Leap 15.5

pkg:rpm/opensuse/kernel-syms&distro=openSUSE%20Leap%2015.5

Vulnerabilities (1,895)

  • CVE-2022-48632Apr 28, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: i2c: mlxbf: prevent stack overflow in mlxbf_i2c_smbus_start_transaction() memcpy() is called in a loop while 'operation->length' upper bound is not checked and 'data_idx' also increments.

  • CVE-2022-48631Apr 28, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: ext4: fix bug in extents parsing when eh_entries == 0 and eh_depth > 0 When walking through an inode extents, the ext4_ext_binsearch_idx() function assumes that the extent header has been previously validated.

  • CVE-2024-26928Apr 28, 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: smb: client: fix potential UAF in cifs_debug_files_proc_show() Skip sessions that are being teared down (status == SES_EXITING) to avoid UAF.

  • CVE-2024-26927Apr 28, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Add some bounds checking to firmware data Smatch complains about "head->full_size - head->header_size" can underflow. To some extent, we're always going to have to trust the firmware a bit. However

  • CVE-2023-52646Apr 26, 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: aio: fix mremap after fork null-deref Commit e4a0d3e720e7 ("aio: Make it possible to remap aio ring") introduced a null-deref if mremap is called on an old aio mapping after fork as mm->ioctx_table will be set

  • CVE-2024-26925MedApr 25, 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: netfilter: nf_tables: release mutex after nft_gc_seq_end from abort path The commit mutex should not be released during the critical section between nft_gc_seq_begin() and nft_gc_seq_end(), otherwise, async GC

  • CVE-2024-26923MedApr 25, 2024
    affected < 5.14.21-150500.55.73.1fixed 5.14.21-150500.55.73.1

    In the Linux kernel, the following vulnerability has been resolved: af_unix: Fix garbage collector racing against connect() Garbage collector does not take into account the risk of embryo getting enqueued during the garbage collection. If such embryo has a peer that carries SCM

  • CVE-2024-26922Apr 23, 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/amdgpu: validate the parameters of bo mapping operations more clearly Verify the parameters of amdgpu_vm_bo_(map/replace_map/clearing_mappings) in one common place.

  • CVE-2024-26921Apr 18, 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: inet: inet_defrag: prevent sk release while still in use ip_local_out() and other functions can pass skb->sk as function argument. If the skb is a fragment and reassembly happens before such function call retu

  • CVE-2024-26920MedApr 17, 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: tracing/trigger: Fix to return error if failed to alloc snapshot Fix register_snapshot_trigger() to return error code if it failed to allocate a snapshot instead of 0 (success). Unless that, it will register sn

  • CVE-2024-26919Apr 17, 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: ulpi: Fix debugfs directory leak The ULPI per-device debugfs root is named after the ulpi device's parent, but ulpi_unregister_interface tries to remove a debugfs directory named after the ulpi device itse

  • CVE-2024-26917Apr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: fcoe: Fix potential deadlock on &fip->ctlr_lock" This reverts commit 1a1975551943f681772720f639ff42fbaa746212. This commit causes interrupts to be lost for FCoE devices, since it changed sp

  • CVE-2024-26916Apr 17, 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: Revert "drm/amd: flush any delayed gfxoff on suspend entry" commit ab4750332dbe ("drm/amdgpu/sdma5.2: add begin/end_use ring callbacks") caused GFXOFF control to be used more heavily and the codepath that was r

  • CVE-2024-26915Apr 17, 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/amdgpu: Reset IH OVERFLOW_CLEAR bit Allows us to detect subsequent IH ring buffer overflows as well.

  • CVE-2023-52645Apr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: pmdomain: mediatek: fix race conditions with genpd If the power domains are registered first with genpd and *after that* the driver attempts to power them on in the probe sequence, then it is possible that a ra

  • CVE-2024-26907HigApr 17, 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: RDMA/mlx5: Fix fortify source warning while accessing Eth segment ------------[ cut here ]------------ memcpy: detected field-spanning write (size 56) of single field "eseg->inline_hdr.start" at /var/lib/dkms

  • CVE-2024-26903MedApr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security During our fuzz testing of the connection and disconnection process at the RFCOMM layer, we discovered this bug. By comparing the packets from a no

  • CVE-2024-26901MedApr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: do_sys_name_to_handle(): use kzalloc() to fix kernel-infoleak syzbot identified a kernel information leak vulnerability in do_sys_name_to_handle() and issued the following report [1]. [1] "BUG: KMSAN: kernel-i

  • CVE-2024-26898HigApr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: aoe: fix the potential use-after-free problem in aoecmd_cfg_pkts This patch is against CVE-2023-6270. The description of cve is: A flaw was found in the ATA over Ethernet (AoE) driver in the Linux kernel.

  • CVE-2024-26897MedApr 17, 2024
    affected < 5.14.21-150500.55.62.1fixed 5.14.21-150500.55.62.1

    In the Linux kernel, the following vulnerability has been resolved: wifi: ath9k: delay all of ath9k_wmi_event_tasklet() until init is complete The ath9k_wmi_event_tasklet() used in ath9k_htc assumes that all the data structures have been fully initialised by the time it runs. H

Page 66 of 95