VYPR

rpm package

suse/kernel-docs&distro=SUSE Linux Enterprise Server 15 SP4-LTSS

pkg:rpm/suse/kernel-docs&distro=SUSE%20Linux%20Enterprise%20Server%2015%20SP4-LTSS

Vulnerabilities (2,830)

  • CVE-2024-46854HigSep 27, 2024
    affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

    In the Linux kernel, the following vulnerability has been resolved: net: dpaa: Pad packets to ETH_ZLEN When sending packets under 60 bytes, up to three bytes of the buffer following the data may be leaked. Avoid this by extending all packets to ETH_ZLEN, ensuring nothing is lea

  • CVE-2024-46849HigSep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: ASoC: meson: axg-card: fix 'use-after-free' Buffer 'card->dai_link' is reallocated in 'meson_card_reallocate_links()', so move 'pad' pointer initialization after this function when memory is already reallocated

  • CVE-2024-46813HigSep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check link_index before accessing dc->links[] [WHY & HOW] dc->links[] has max size of MAX_LINKS and NULL is return when trying to access with out-of-bound index. This fixes 3 OVERRUN and 1 RES

  • CVE-2024-46818Sep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check gpio_id before used as array index [WHY & HOW] GPIO_ID_UNKNOWN (-1) is not a valid value for array index and therefore should be checked in advance. This fixes 5 OVERRUN issues reported

  • CVE-2024-46817Sep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when stream nums greater than 6 [Why] Coverity reports OVERRUN warning. Should abort amdgpu_dm initialize. [How] Return failure to amdgpu_dm_init.

  • CVE-2024-46816Sep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Stop amdgpu_dm initialize when link nums greater than max_links [Why] Coverity report OVERRUN warning. There are only max_links elements within dc->links. link count could up to AMDGPU_DM_MAX_D

  • CVE-2024-46815Sep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check num_valid_sets before accessing reader_wm_sets[] [WHY & HOW] num_valid_sets needs to be checked to avoid a negative index when accessing reader_wm_sets[num_valid_sets - 1]. This fixes an

  • CVE-2024-46814Sep 27, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: drm/amd/display: Check msg_id before processing transcation [WHY & HOW] HDCP_MESSAGE_ID_INVALID (-1) is not a valid msg_id nor is it a valid array index, and it needs checking before used. This fixes 4 OVERRUN

  • CVE-2022-48945Sep 23, 2024
    affected < 5.14.21-150400.24.136.1fixed 5.14.21-150400.24.136.1

    In the Linux kernel, the following vulnerability has been resolved: media: vivid: fix compose size exceed boundary syzkaller found a bug: BUG: unable to handle page fault for address: ffffc9000a3b1000 #PF: supervisor write access in kernel mode #PF: error_code(0x0002) - not

  • CVE-2024-46800Sep 18, 2024
    affected < 5.14.21-150400.24.170.1fixed 5.14.21-150400.24.170.1

    In the Linux kernel, the following vulnerability has been resolved: sch/netem: fix use after free in netem_dequeue If netem_dequeue() enqueues packet to inner qdisc and that qdisc returns __NET_XMIT_STOLEN. The packet is dropped but qdisc_tree_reduce_backlog() is not called to

  • CVE-2024-46784Sep 18, 2024
    affected < 5.14.21-150400.24.164.1fixed 5.14.21-150400.24.164.1

    In the Linux kernel, the following vulnerability has been resolved: net: mana: Fix error handling in mana_create_txq/rxq's NAPI cleanup Currently napi_disable() gets called during rxq and txq cleanup, even before napi is enabled and hrtimer is initialized. It causes kernel pani

  • CVE-2024-46774Sep 18, 2024
    affected < 5.14.21-150400.24.136.1fixed 5.14.21-150400.24.136.1

    In the Linux kernel, the following vulnerability has been resolved: powerpc/rtas: Prevent Spectre v1 gadget construction in sys_rtas() Smatch warns: arch/powerpc/kernel/rtas.c:1932 __do_sys_rtas() warn: potential spectre issue 'args.args' [r] (local cap) The 'nargs' and '

  • CVE-2024-46716Sep 18, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: dmaengine: altera-msgdma: properly free descriptor in msgdma_free_descriptor Remove list_del call in msgdma_chan_desc_cleanup, this should be the role of msgdma_free_descriptor. In consequence replace list_add_

  • CVE-2024-46674Sep 13, 2024
    affected < 5.14.21-150400.24.136.1fixed 5.14.21-150400.24.136.1

    In the Linux kernel, the following vulnerability has been resolved: usb: dwc3: st: fix probed platform device ref count on probe error path The probe function never performs any paltform device allocation, thus error path "undo_platform_dev_alloc" is entirely bogus. It drops t

  • CVE-2024-45016MedSep 11, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: netem: fix return value if duplicate enqueue fails There is a bug in netem_enqueue() introduced by commit 5845f706388a ("net: netem: fix skb length BUG_ON in __skb_to_sgvec") that can lead to a use-after-free.

  • CVE-2024-45026Sep 11, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: s390/dasd: fix error recovery leading to data corruption on ESE devices Extent Space Efficient (ESE) or thin provisioned volumes need to be formatted on demand during usual IO processing. The dasd_ese_needs_fo

  • CVE-2024-45021Sep 11, 2024
    affected < 5.14.21-150400.24.136.1fixed 5.14.21-150400.24.136.1

    In the Linux kernel, the following vulnerability has been resolved: memcg_write_event_control(): fix a user-triggerable oops we are *not* guaranteed that anything past the terminating NUL is mapped (let alone initialized with anything sane).

  • CVE-2024-45013Sep 11, 2024
    affected < 5.14.21-150400.24.141.1fixed 5.14.21-150400.24.141.1

    In the Linux kernel, the following vulnerability has been resolved: nvme: move stopping keep-alive into nvme_uninit_ctrl() Commit 4733b65d82bd ("nvme: start keep-alive after admin queue setup") moves starting keep-alive from nvme_start_ctrl() into nvme_init_ctrl_finish(), but d

  • CVE-2024-44987HigSep 4, 2024
    affected < 5.14.21-150400.24.194.1fixed 5.14.21-150400.24.194.1

    In the Linux kernel, the following vulnerability has been resolved: ipv6: prevent UAF in ip6_send_skb() syzbot reported an UAF in ip6_send_skb() [1] After ip6_local_out() has returned, we no longer can safely dereference rt, unless we hold rcu_read_lock(). A similar issue has

  • CVE-2024-45003Sep 4, 2024
    affected < 5.14.21-150400.24.133.1fixed 5.14.21-150400.24.133.1

    In the Linux kernel, the following vulnerability has been resolved: vfs: Don't evict inode under the inode lru traversing context The inode reclaiming process(See function prune_icache_sb) collects all reclaimable inodes and mark them with I_FREEING flag at first, at that time,

Page 97 of 142