VYPR

rpm package

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

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

Vulnerabilities (1,350)

  • CVE-2021-46929Feb 27, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: sctp: use call_rcu to free endpoint This patch is to delay the endpoint free by calling call_rcu() to fix another use-after-free issue in sctp_sock_dump(): BUG: KASAN: use-after-free in __lock_acquire+0x36d9

  • CVE-2021-46924Feb 27, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: NFC: st21nfca: Fix memory leak in device probe and remove 'phy->pending_skb' is alloced when device probe, but forgot to free in the error handling path and remove path, this cause memory leak as follows: unre

  • CVE-2021-46922Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: KEYS: trusted: Fix TPM reservation for seal/unseal The original patch 8c657a0590de ("KEYS: trusted: Reserve TPM for seal and unseal operations") was correct on the mailing list: https://lore.kernel.org/linux-i

  • CVE-2021-46921Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: locking/qrwlock: Fix ordering in queued_write_lock_slowpath() While this code is executed with the wait_lock held, a reader can acquire the lock without holding wait_lock. The writer side loops checking the va

  • CVE-2021-46920Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: Fix clobbering of SWERR overflow bit on writeback Current code blindly writes over the SWERR and the OVERFLOW bits. Write back the bits actually read instead so the driver avoids clobbering the

  • CVE-2021-46919Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix wq size store permission state WQ size can only be changed when the device is disabled. Current code allows change when device is enabled but wq is disabled. Change the check to detect devi

  • CVE-2021-46918Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: clear MSIX permission entry on shutdown Add disabling/clearing of MSIX permission entries on device shutdown to mirror the enabling of the MSIX entries on probe. Current code left the MSIX enab

  • CVE-2021-46917Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: idxd: fix wq cleanup of WQCFG registers A pre-release silicon erratum workaround where wq reset does not clear WQCFG registers was leaked into upstream code. Use wq reset command instead of blasting

  • CVE-2021-46915Feb 27, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_limit: avoid possible divide error in nft_limit_init div_u64() divides u64 by u32. nft_limit_init() wants to divide u64 by u64, use the appropriate math function (div64_u64) divide error: 0000

  • CVE-2021-46914Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: ixgbe: fix unbalanced device enable/disable in suspend/resume pci_disable_device() called in __ixgbe_shutdown() decreases dev->enable_cnt by 1. pci_enable_device_mem() which increases dev->enable_cnt by 1, was

  • CVE-2021-46911Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: ch_ktls: Fix kernel panic Taking page refcount is not ideal and causes kernel panic sometimes. It's better to take tx_ctx lock for the complete skb transmit, to avoid page cleanup if ACK received in middle.

  • CVE-2021-46909Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: ARM: footbridge: fix PCI interrupt mapping Since commit 30fdfb929e82 ("PCI: Add a call to pci_assign_irq() in pci_device_probe()"), the PCI code will call the IRQ mapping function whenever a PCI driver is probe

  • CVE-2021-46908Feb 27, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: bpf: Use correct permission flag for mixed signed bounds arithmetic We forbid adding unknown scalars with mixed signed bounds due to the spectre v1 masking mitigation. Hence this also needs bypass_spec_v1 flag

  • CVE-2023-52474Feb 26, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: IB/hfi1: Fix bugs with non-PAGE_SIZE-end multi-iovec user SDMA requests hfi1 user SDMA request processing has two bugs that can cause data corruption for user SDMA requests that have multiple payload iovecs whe

  • CVE-2021-46906Feb 26, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: HID: usbhid: fix info leak in hid_submit_ctrl In hid_submit_ctrl(), the way of calculating the report length doesn't take into account that report->size can be zero. When running the syzkaller reproducer, a rep

  • CVE-2019-25162Feb 26, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: i2c: Fix a potential use after free Free the adap structure only after we are done using it. This patch just moves the put_device() down a bit to avoid the use after free. [wsa: added comment to the code, adde

  • CVE-2022-48626Feb 25, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: moxart: fix potential use-after-free on remove path It was reported that the mmc host structure could be accessed after it was freed in moxart_remove(), so fix this by saving the base register of the device and

  • CVE-2021-46905Feb 25, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: net: hso: fix NULL-deref on disconnect regression Commit 8a12f8836145 ("net: hso: fix null-ptr-deref during tty device unregistration") fixed the racy minor allocation reported by syzbot, but introduced an unco

  • CVE-2021-46904Feb 25, 2024
    affected < 5.3.18-150300.59.153.2fixed 5.3.18-150300.59.153.2

    In the Linux kernel, the following vulnerability has been resolved: net: hso: fix null-ptr-deref during tty device unregistration Multiple ttys try to claim the same the minor number causing a double unregistration of the same device. The first unregistration succeeds but the n

  • CVE-2023-52470Feb 25, 2024
    affected < 5.3.18-150300.59.158.1fixed 5.3.18-150300.59.158.1

    In the Linux kernel, the following vulnerability has been resolved: drm/radeon: check the alloc_workqueue return value in radeon_crtc_init() check the alloc_workqueue return value in radeon_crtc_init() to avoid null-ptr-deref.

Page 54 of 68