VYPR

rpm package

suse/kernel-source&distro=SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS

pkg:rpm/suse/kernel-source&distro=SUSE%20Linux%20Enterprise%20High%20Performance%20Computing%2015%20SP5-LTSS

Vulnerabilities (2,318)

  • CVE-2022-49288HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix races among concurrent prealloc proc writes We have no protection against concurrent PCM buffer preallocation changes via proc files, and it may potentially lead to UAF or some weird problem. Th

  • CVE-2022-49287HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: tpm: fix reference counting for struct tpm_chip The following sequence of operations results in a refcount warning: 1. Open device /dev/tpmrm. 2. Remove module tpm_tis_spi. 3. Write a TPM command to the file d

  • CVE-2022-49286MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: tpm: use try_get_ops() in tpm-space.c As part of the series conversion to remove nested TPM operations: https://lore.kernel.org/all/20190205224723.19671-1-jarkko.sakkinen@linux.intel.com/ exposure of the chip

  • CVE-2022-49285MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: iio: accel: mma8452: use the correct logic to get mma8452_data The original logic to get mma8452_data is wrong, the *dev point to the device belong to iio_dev. we can't use this dev to find the correct i2c_clie

  • CVE-2022-49283MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: firmware: sysfb: fix platform-device leak in error path Make sure to free the platform device also in the unlikely event that registration fails.

  • CVE-2022-49281MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: cifs: fix handlecache and multiuser In multiuser each individual user has their own tcon structure for the share and thus their own handle for a cached directory. When we umount such a share we much make sure t

  • CVE-2022-49280MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: NFSD: prevent underflow in nfssvc_decode_writeargs() Smatch complains: fs/nfsd/nfsxdr.c:341 nfssvc_decode_writeargs() warn: no lower bound on 'args->len' Change the type to unsigned to prevent this issue.

  • CVE-2022-49279MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: NFSD: prevent integer overflow on 32 bit systems On a 32 bit system, the "len * sizeof(*p)" operation can have an integer overflow.

  • CVE-2022-49278HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: remoteproc: Fix count check in rproc_coredump_write() Check count for 0, to avoid a potential underflow. Make the check the same as the one in rproc_recovery_write().

  • CVE-2022-49277MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_do_mount_fs If jffs2_build_filesystem() in jffs2_do_mount_fs() returns an error, we can observe the following kmemleak report: -------------------------------------------- unref

  • CVE-2022-49276MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: jffs2: fix memory leak in jffs2_scan_medium If an error is returned in jffs2_scan_eraseblock() and some memory has been added to the jffs2_summary *s, we can observe the following kmemleak report: ------------

  • CVE-2022-49275HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: can: m_can: m_can_tx_handler(): fix use after free of skb can_put_echo_skb() will clone skb then free the skb. Move the can_put_echo_skb() for the m_can version 3.0.x directly before the start of the xmit in ha

  • CVE-2022-49274MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: ocfs2: fix crash when mount with quota enabled There is a reported crash when mounting ocfs2 with quota enabled. RIP: 0010:ocfs2_qinfo_lock_res_init+0x44/0x50 [ocfs2] Call Trace: ocfs2_local_read_info+

  • CVE-2022-49273MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: rtc: pl031: fix rtc features null pointer dereference When there is no interrupt line, rtc alarm feature is disabled. The clearing of the alarm feature bit was being done prior to allocations of ldata->rtc dev

  • CVE-2022-49272MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: ALSA: pcm: Fix potential AB/BA lock with buffer_mutex and mmap_lock syzbot caught a potential deadlock between the PCM runtime->buffer_mutex and the mm->mmap_lock. It was brought by the recent fix to cover the

  • CVE-2022-49271MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: cifs: prevent bad output lengths in smb2_ioctl_query_info() When calling smb2_ioctl_query_info() with smb_query_info::flags=PASSTHRU_FSCTL and smb_query_info::output_buffer_length=0, the following would return

  • CVE-2022-49270HigFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: dm: fix use-after-free in dm_cleanup_zoned_dev() dm_cleanup_zoned_dev() uses queue, so it must be called before blk_cleanup_disk() starts its killing: blk_cleanup_disk->blk_cleanup_queue()->kobject_put()->blk_

  • CVE-2022-49269MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: can: isotp: sanitize CAN ID checks in isotp_bind() Syzbot created an environment that lead to a state machine status that can not be reached with a compliant CAN ID address configuration. The provided address i

  • CVE-2022-49268MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: SOF: Intel: Fix NULL ptr dereference when ENOMEM Do not call snd_dma_free_pages() when snd_dma_alloc_pages() returns -ENOMEM because it leads to a NULL pointer dereference bug. The dmesg says: [ T1387

  • CVE-2022-49266MedFeb 26, 2025
    affected < 5.14.21-150500.55.100.1fixed 5.14.21-150500.55.100.1

    In the Linux kernel, the following vulnerability has been resolved: block: fix rq-qos breakage from skipping rq_qos_done_bio() a647a524a467 ("block: don't call rq_qos_ops->done_bio if the bio isn't tracked") made bio_endio() skip rq_qos_done_bio() if BIO_TRACKED is not set. Whi

Page 93 of 116